Changed behavior of Shared Object on iOS in AIR 3.5

With AIR 3.5 the path of shared objects changed than it used to be in AIR 3.4, following illustrates the difference between paths:
In AIR 3.4:
AppName/Library/Application Support/com.namecompany.name/Local Store/ #SharedObjects/Filename.swf
where Filename.swf comes from the <Filename> tag of app-xml.

In AIR 3.5:
AppName/Library/Application Support/com.namecompany.name/Local Store/ #SharedObjects/Content.swf
where Content.swf comes from the <Content> tag of app-xml which contains
the name of root SWF of app.

This issue is fixed in 3.6(labs), so when user will update his/her app from AIR 3.4 to 3.6, then application will not lose any data which is stored with shared object. While any new App which will be published with next release of AIR will have shared object path:
AppName/Library/Application Support/com.namecompany.name/Local Store/ #SharedObjects/Content.swf

Workaround for AIR 3.5:

For those app-developers who are going to publish their app with AIR 3.5 there is a workaround for them.Since now shared object path is taken from tag <Content> rather than tag <Filename> so you can rename your root SWF to Filename.swf and also provide the same to tag. For example:
In AIR 3.4 :
<Filename>MysharedObject</Filename>
<Content>Root.swf</Content>

Now in AIR 3.5, rename it like following:
<Filename>MysharedObject</Filename>
<Content>MysharedObject.swf</Content>

and also rename Root.swf to MysharedObject.swf.
By this way the data of the app will be saved when it will be updated from AIR 3.4 to AIR 3.5.

We would like to hear your feedback, please let us know if you face any issues.

One Response to Changed behavior of Shared Object on iOS in AIR 3.5

  1. Robert says:

    I guess that answers my question here: http://stackoverflow.com/questions/16737843/adobe-air-sharedobject-android-ios-on-update-not-found

    My solution for transmitting an SO via network connection to remote server: http://stackoverflow.com/questions/16139947/air-android-mobile-same-sharedobject-for-different-apps/16738169#16738169

    My question is, is there a location on iOS where I could store a backup ByteArray file that is public to all applications?