The same steps apply, only that in step 2. If you use a version control system (VCS)-which I really hope that you do-you can also just build & install a previous version before updating with your latest snapshot. You can either modify the release config to be debuggable while testing, or create a third buildType that is release signed, but debuggable.
If you properly configured your adle file you can just press the Play button in Android Studio after selecting the release build variant.
You can still attach a debugger and check what's going on in case there are more serious errors. keep in mind that you only need an app that is signed with your release keystore, but it can still be debuggable. Populate your app with data, as a user would, so that you can properly test the update. You have to at least open your app once, or it will not run. Afterwards you just install the app as any user would in 2. Uninstallation is the best way to make sure the app data is cleared.
is to make sure you get the PlayStore version as your users would. This has to be signed with your release keystore or the update will fail Open the app, log in, do whatever it needs to fill your database and settings.Uninstall any current installation of your app.To test an app update the most basic way would be to. You only want to use the beta channel once you are done testing and want to start receiving user feedback. You really don't need the beta channel to test app updates. So the less programing and command prompt usage needed the solution is the better. It would be nice if I could do this with other people testing my app. Is there a more sophisticated way to test app version updates? The only way (as far as I concern) is to remove the beta tester from the beta testing list (could take hours to refresh in Google Play systems), re-download the 1.0 application, re-add the tester to the beta testing list, (again waiting hours) and download the new 1.2 application. Install a the current stable version (1.0) to the tester's device, then update the application to (1.1) - let's say we got an error during the playtest of the new updated version (1.1), I repair it (1.2) and I would like to repeat the procedure, I would like to install the 1.0 stable app to the tester's device and yet again I would like to update the app to 1.2 (with the resolved error) I have tried to use the Google Play Store's beta testing feature, but the problem is there is no effective way (or at least I haven't found one yet) to do the following:
In the new version (1.1) I would like to upgrade the database with new columns.ĭatabase upgrading is a common crash in my application because users in previous version (1.0) doesn't have the new columns in the database. Let's say I have the app in Google Play Store with version 1.0.
0 kommentar(er)
