Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Whilst in the debugging stage and using Eclipse I install myappv1. Then later I install myappv2 (both have the same package name). Because the name is different Android installs them side by side. Will the preferences established by myappv1 be available to myappv2? I see that if I just install a later version off myappv1 it replaces the original and the prefs seem to persist.
Yes, application preferences are persistent across updates. However, you need to understand how Android application signing and versioning works in order to ensure that updates to your application are treated as such.
In short…
When you release an update to your app, you must sign it with the same key as you used on all earlier versions (that way Android knows it’s the same app). To let Android know that the version has changed, increment the value of the
android:versionCodevalue inAndroidManifest.xml(You should also update the user-displayableandroid:versionNamevalue).For more details, check out http://developer.android.com/guide/publishing/app-signing.html and http://developer.android.com/guide/publishing/versioning.html