As you may have noticed, we have delayed distribution of webOS 1.4.5. We started a roll-out with deployment on the German O2 and French SFR networks at the end of June, but thanks to reports from you and your users, we suspended deployment to look at a problem that was affecting PDK applications and their ability to save and restore user data.
We've investigated the problem, and it ends up that a key system file, /etc/fstab, wasn't being updated by our over-the-air update mechanism. We do most of our testing using applications that re-flash the whole device, so we did not catch this OTA-specific issue. We do perform some specific OTA update tests, but these unfortunately didn't include deep testing of PDK-based applications. The result of this bug is that the /media/internal drive is marked as read-only for PDK applications in webOS 1.4.5.
This was not our intention. PDK apps that use the PDL_GetDataFilePath API to find a location to write out data files will get a location that isn't writable.
We've spent the last week attempting to address this issue in a way that would not require restarting the carrier certification process, but we've concluded that this is not possible. Restarting certification would delay 1.4.5 substantially and could result in some wireless operators not taking the update at all. Consequently, we've decided to go ahead with the 1.4.5 deployment, despite the bug. In making this decision, we looked closely at the current crop of PDK apps and determined that a relatively small number of apps are affected. If your app is affected, you will need to update it to save preference and configuration data in your own application directory, not in /media/internal.
You can get access to this location by using the PDL_GetCallingPath API. Any files and folders created here will not be visible to the user, but will be preserved when your app is upgraded. They will also be removed if the user deletes your app from the device, unlike the folders in /media/internal. Please make any updates and resubmit your PDK app as soon as possible
in order to have a clean upgrade cycle and to avoid user problems. If you're app has already been distributed, you should have it look for data first in the old location, but all writes should go back to your application directory. If you need to have a current submission rejected so you can resubmit, please mail email@example.com
and it will be escalated.
We will be updating our online documentation to warn about this problem, and the next OS update after 1.4.5 should restore write access to /media/internal. We're sorry that you have to deal with this, and we've revised our QA procedures to include more checks that the files on the device after an OTA update exactly match what is provided by a full webOSDoctor-based restore.