iOS5.0.1 ‘Do Not Backup’ attribute for saved files?

With AIR 3.6 latest prerelease,

A new property, preventBackup is introduced in the File API, which when set prevents a file or a folder from getting backed up on the iCloud. This property works on iOS 5.1 devices and later.

Another static property, File.cacheDirectory has been added, which points to the <APPLICATION_HOME>/Library/Caches directory on iOS devices, and files in this directory are not backed up. So, the above workaround is not required.

You can find additional details on this feature here<http://labsdownload.adobe.com/pub/labs/flashruntimes/shared/air3-6_flashplayer11-6_releasenotes.pdf>

I know that shared objects not run in iOS 5.1 rules (because it put the content in "Libray/Application Support" instead "Libray/Caches").

Saddly my app save all local preferences in shared objects. I decided it because its little info and its very easy to add data and recover it (instead multiple items with key-value pairs like ints, strings, booleans, objects, array, arraycollections).

Saumitra in your blog you comment:

"we currently have is to "Not to use LSO"...or you may want to create some class like MyLSO which provides the similar functionality using File APIs(which in turn use the following solution)"

In your example you add some string to FileStream using writeUTFBytes() 

Its possible to use an key-value pairs in this solution like in Shared Object?

Its possible to put an arraycollection like in Shared Object?

Or you would recommend me switch to SQLite database?

Thanks so much!

As you comment I have find the solution 2 days ago at your blog ;-), I ha ve updated my library and it seems to be ok, I need to test the library in android ( because I have changed the way I emty the tmp folder) , an after I will update...

I will send you some test, this way you can see if sure is ok...

Thanks anyway 4 you post.

At first we also sought to find a solution without additional workarounds.

So we migrated our Flex/AIR projects away from File.applicationStorageDirectory to File.documentsDirectory.

I believe that will ok if your data is user generated & critical. This method uses the current AIR framework with no extra workarounds.

But if like us you are downloading data and need to store this without the danger of being deleted then the use of File.documentsDirectory in your App will get Rejected.

Our 'Do Not Backup' ANE should allow you to modify your existing File code slightly without a major rewrite because we have also developed a helper File storage package (ie.jampot.device.DataStorage) which uses File objects itself to do the work.

A simple way to do this is a quick find and replace for:

"File.applicationStorageDirectory(" with "DataStorage.filePrivate("

Then after a file has been saved simply apply the iOS Do Not Backup ANE to that directory.

private var iCloud : MobileBackup = new MobileBackup();

iCloud.doNotBackup( DataStorage.filePrivate.nativePath );

Yes it would be nice to have this built-in to the AIR framework, but for now the bottom line is even if you use Xcode you would still have to to rewrite parts of your code.

David

JamPot.ie

PS. Looks like a nice project you are working on, I'll have to check it out