Skip to main content
Inspiring
May 28, 2012
Answered

What happens to files in my users' applicationStorageDirectory when I upload an update for my iOS Ap

  • May 28, 2012
  • 1 reply
  • 1222 views

I have an iPad app being sold in the iOS App Store. I use File.applicationStorageDirectory.resolvePath to save some XML files locally to the user's iPad (stuff like user's high scores when playing in offline mode).

What will happen to these files for my users if I upload a new app update to App Store? Will they get deleted because the update is a fresh install of the app, or will they be left alone?

This topic has been closed for replies.
Correct answer

hehehe, that was one of my first questions I got when I started building apps on air for mobile. The answer is; your binary will be updated BUT all the files of your app saved dynamically will persists, everytime you save anything from your app it is stored in a location linked to your app ID (com.yourappname.blah.blah) which is only removed when the user removes the app from the device, otherwise it will persists even if you submit a new binary to the store and the user updates it. Does it make sense? I am doing the same on Traffic Wonder and it worked transparently when I made a small update from version 1.0.0 to 1.0.1 (ipad3 compatibility), so no worries, unless your new binary reads the old data in a different way

1 reply

Correct answer
May 28, 2012

hehehe, that was one of my first questions I got when I started building apps on air for mobile. The answer is; your binary will be updated BUT all the files of your app saved dynamically will persists, everytime you save anything from your app it is stored in a location linked to your app ID (com.yourappname.blah.blah) which is only removed when the user removes the app from the device, otherwise it will persists even if you submit a new binary to the store and the user updates it. Does it make sense? I am doing the same on Traffic Wonder and it worked transparently when I made a small update from version 1.0.0 to 1.0.1 (ipad3 compatibility), so no worries, unless your new binary reads the old data in a different way

Inspiring
May 28, 2012

Thanks a bunch. I was beginning to worry that the answer couldn't be found anywhere except by trying and potentially killing my users' offline data.