However the documentation states, and I have confirmed with testing, that a restore will only occur either when the device is restored and the restore app data process is triggered. I recently needed to take advantage of these features, I was able to uncover documentation and upon extensive testing this is what I have been able to deduce:Īndroid:allowbackup - will backup local app data on the device it is located on.Īndroid:fullBackupContent - is used in conjunction with Google's backup restore api and CAN be controlled via an xml file to specify what exactly to backup, as well as a BackupManager class you may implement for further control over the process. I'd expect this to be an opt-in feature but.seems like it might be on by default for apps which don't specify the value either way. Once we explicitly set the value to false, all seems to work. We've modified our AndroidManifest by adding the following two lines: android:allowBackup="false"Īfter adding them, our AndroidManifest contained the following xml: Since I don't know exactly when backups and restores occur this feature seems to cause only problems. The backup also seemed to overwrite newer data when launching from Visual Studio, and we have reports of users using the release build of our app and also getting newer data overwritten by the backups. It's also worth noting that we never explicitly told the app to store a backup. It didn't matter if I simply stopped and re-ran it from VS, or if I completely uninstalled the app and reinstalled it. When developing my Android app (using Xamarin), I noticed that whenever I'd re-launch the app from Visual Studio, my data would revert back to data from a few months ago. Greywolf82's answer is correct but I want to add some info to this.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |