Just a heads up for anybody with an app in the store that saves any kind of data to its documents directory. My first update was posted to the store today, and I have had a few users report that their data is lost after an update. I know that this does not always happen, as I was able to update the app on my personal phone (using the App Store app on the phone) without losing data, but at least one user followed the exact same process and did lose their data.
37 replies
NSKeyedArchiver in my case.
SQLite for me.
This is freaking me out, has Apple responded to anyone on this issue? Specifically .sql files...
It is still happening, as I released an update since the last firmware update and still had a few reports of it. In my case the data is stored in an sqlite db, but that is irrelevant. The app's Documents directory (and presumably everything else) is infrequently getting wiped out during updates and there is no rhyme or reason as to why it does or does not happen.
Doug,
My data is being stored in an SQLite database in the application's documents directory. And I can't disagree with you more about the NSUserDefaults issue -- a user's preferences should not be considered disposable. Maybe on another platform they should but, but that seems entirely counterintuitive to the experience that Apple users expect from their platform.
I filed a Radar on this (dupe 6108734 if you're having the same issues), but haven't received any response yet.
An app upgrade should be a seamless, painless experience, without worry or expectation of calamity. Full stop.
Chris
My data is being stored in an SQLite database in the application's documents directory. And I can't disagree with you more about the NSUserDefaults issue -- a user's preferences should not be considered disposable. Maybe on another platform they should but, but that seems entirely counterintuitive to the experience that Apple users expect from their platform.
I filed a Radar on this (dupe 6108734 if you're having the same issues), but haven't received any response yet.
An app upgrade should be a seamless, painless experience, without worry or expectation of calamity. Full stop.
Chris
We've had it happen, but not consistently.
What's worrying is that reviews have crept on to the App Store blaming us (the developers) for the data loss problem, and negatively effecting our star rating on the App Store. This is an Apple bug and totally beyond our control.
What's worrying is that reviews have crept on to the App Store blaming us (the developers) for the data loss problem, and negatively effecting our star rating on the App Store. This is an Apple bug and totally beyond our control.
My own experience thus far has been that:
1) If I update from iTunes with a backup, I'm fine.
2) If I update from the App Store on the phone, I end up briefly with two copies of the app... and the old one (along with my data) goes away to be replaced by the new one. (I also have to rearrange my springboard icons to get the new one back where the old one was. Grr!)
2a) If I then sync with iTunes /before running the app/, it restores the data from my iTunes backup.
2b) If I download the app and run it before synching with iTunes, new data is created and I am in trouble.
...this is just my own observations thus far, I haven't really tried to put together a firm list or really tested the theory. But maybe this provides a jumping-off point for others...
1) If I update from iTunes with a backup, I'm fine.
2) If I update from the App Store on the phone, I end up briefly with two copies of the app... and the old one (along with my data) goes away to be replaced by the new one. (I also have to rearrange my springboard icons to get the new one back where the old one was. Grr!)
2a) If I then sync with iTunes /before running the app/, it restores the data from my iTunes backup.
2b) If I download the app and run it before synching with iTunes, new data is created and I am in trouble.
...this is just my own observations thus far, I haven't really tried to put together a firm list or really tested the theory. But maybe this provides a jumping-off point for others...
This has happened to my users as well. I verified that the update went smoothly for me, but a few people reported having the SQLite database wiped out.
Has 2.0.2 update fixed this issue?
Unless I confirm this, I can't update my app ... although the next version is ready.
Unless I confirm this, I can't update my app ... although the next version is ready.
With nice, detailed release notes like "bug fixes" I guess we'll never know...
I really hope Apple fixes this with the next update. My app had another update released a couple days ago, and received yet a few more reports of data loss. I feel like charging Apple for all of the support I have provided people due to the data loss and app crashing issues.
Message was edited by: admanimal
Message was edited by: admanimal
I have been unable to update my app to the next version (which has already been completed) since I have received data loss reports when I updated the app before. My app is user data centric and data loss is fatal.
Once our app is launched, we are responsible for troubles. But what can we do when our app hasn't been started, or even hasn't been installed?
This is installer's problem and Apple must know it. Apple has to protect our user's data by announcing this issue.
Once our app is launched, we are responsible for troubles. But what can we do when our app hasn't been started, or even hasn't been installed?
This is installer's problem and Apple must know it. Apple has to protect our user's data by announcing this issue.
I got an email response from Apple today regarding the radar bug I had filed on this issue. It's the fairly stock "we think this is fixed with the latest OS update":
"We believe this issue has been addressed in OS X iPhone 2.1. ... Please let us know whether or not you continue to experience this issue with the newly released software by updating this bug report"
My experience shows that this is not an actual claim that it is fixed. I get these lots of times after software updates. I think they clear the queue in this manner.
"We believe this issue has been addressed in OS X iPhone 2.1. ... Please let us know whether or not you continue to experience this issue with the newly released software by updating this bug report"
My experience shows that this is not an actual claim that it is fixed. I get these lots of times after software updates. I think they clear the queue in this manner.
Does anyone know if this issue has been fixed in OS 2.1?
I don't know because Apple won't approve my app because I warned users to backup before installing updates due to the updater bug. Sat in approval queue for 11 days, then rejection notice, now start all over again.
Data loss after updates