I've just had a problem report regarding an odd issue that is associated with the latest updates.
Battery Guru can write export files (in CSV format) to shared/documents/BatteryGuru. The files are simple text files created with code basically like this:
stream = new FileStream();
stream.openAsync(temp_path, FileMode.WRITE);
# later on in an event handler
stream.writeUTFBytes(...)
# later on in another event handler
stream.close();
The catch is that the files are initially created inside the app's tmp/ folder in the sandbox, and only after they are completely written are they moved to shared/documents/BatteryGuru, with a "temp_path.moveTo(dest, true);"
Under previous versions this worked fine, and files came out looking like this (as seen by "ls -l" via SSH):
-rwxrw---- 1 nobody 1000_shared 3020833 Nov 11 20:25 export-20110720T142136-20110909T235450.csv
These files were visible from the MEDIA network share and could be copied off the PlayBook. They could also be moved around, renamed, etc, just like any other file created in the shared/ folders in the first place.
Under the latest updates, 1.0.8.4985 and 2.0.0.4869, things have changed. Here's what "ls -l" sees on the 1.0.8 unit:
-rw-rw---- 1 100441000 10044 969073 Nov 27 20:21 export-20111110T183253-20111127T202119.csv
On my 2.0.0.4869 unit, here's a similar case:
-rw-rw---- 1 100591000 10059 326405 Nov 27 21:57 export-20111123T185137-20111127T215640.csv
The problem is that these files cannot be read from the MEDIA share, nor in fact are even listed in a directory listing when viewed from there. They cannot be copied, they cannot be opened, except perhaps by the app that wrote them. (I can't check that yet since Battery Guru does not read back its own export files.. I'd have to make a test build to check that.)
When another AIR app (e.g. Files & Folders) attempts to read the file, it reports a 3001 error which means this "File or directory access denied."
When I try it from SSH, I get this:
$ cp export-20111110T183253-20111127T202119.csv ../tempfile
cp: Can't open source file. (export-20111110T183253-20111127T202119.csv): Permission denied
I'm not actually sure the problem is related to my initially writing to tmp/ though. The BatteryGuru/ folder itself is created automatically if it doesn't exist. On my 1.0.8 unit the folder already existed from before, so it looks like this:
drwxrws--- 2 nobody 1000_shared 4096 Nov 27 20:21 BatteryGuru
Under 2.0, where I just did an export for the first time, the new BatteryGuru folder looks like this:
drwxrws--- 2 100591000 1000_shared 4096 Nov 27 21:57 BatteryGuru
I can see that other apps may be affected in a similar fashion, though the basic inability to read the files at all may not be affecting them for some reason... maybe because they aren't writing to a subfolder? Here are two files, one written by the Box.net app, the other by the "native" DocumentsToGo app, for the updated OS, and the earlier one:
# newly written since update to 1.0.8.4985:
-rw-rw-r-- 1 100491000 1000_shared 2016327 Nov 10 21:17 AT32UC3C Series Summary.pdf
-rw-rw-r-- 1 100121000 1000_shared 19968 Nov 16 18:56 BBX Python Todos.doc
# written by 1.0.7:
-rwxrw---- 1 nobody 1000_shared 111705 Nov 11 20:24 GUGO.pdf
-rwxrw---- 1 nobody 1000_shared 12288 Nov 11 20:24 Todo items.doc
Anyone else experiencing an actual problem reading files written by their app to the shared folders?
In particular, could anyone whose app writes to its own subfolder, created in the shared/ folder tree, please check and see whether under the updated OS version(s) they have any issue like mine, where the file is inaccessible though shows in a local directory listing but is invisible when viewed via Samba?
