I have implemented In-app update in my app and followed the below mentioned steps to test it,
Uninstall the original app from device.
Install the app from the Google Play Store
Uninstall the app again.
Generate signed apk with the new feature, with a lower versionCode than Google Play version
Install this apk.
Above mentioned steps will not work in some devices.
So I want to know if there is any alternative way for this testing.
At the end of the document, you should make sure the below conditions:
I hope it helps!
For the in app update feature their are some pre requirements , you need to make sure that the application is already live and installed in your device , one user is already logged In into the app and their is an update coming soon for that app.
For testing the in app update feature of the android application the user needs to follow various steps:
Step - 1 Verify that the app you are testing is live on play store.
Step - 2 Install the application
Step - 3 Login to the app.
Step - 4 Ask the developer to upload the latest build
Step - 5 Open playstore and check whether their is any update for the app.
Step - 6 If their is an update on playstore , Open your app and check for the app update pop up.
Related
I'm trying to test the in-app purchase of a consumable item on Android, but I'm unable to do so, as the item appears as being unavailable in my country:
This only happens when I'm testing on a device connected to Android Studio (which I need to be able to do) - if I instead download the app onto the device, the consumable item appears normally, i.e. as being available.
Some details:
I'm testing on a physical device running Android version 6.0.1
That device is running the latest version of the Google Play application
I'm testing with a user that has been set up both as a track tester and a license tester, and that is also currently signed in on the device
I've made the app available in all available 177 countries and regions
The app does not have a production release, it's only available on the closed testing track
If you have uploaded the build from the closed track, please ensure that you have accepted the test invitation from the invited email or it will show this error.
Step 1: Go to Release -> Testing -> Closed Testing
Step 2: Click on Manage Track
Step 3: Click on Testers tab
Step 4: Scroll to the bottom and you will see 2 options. Copy the link for web and open the link in your phone or browser with the test email you want to test.
Step 5: When you open the link you will have an option to Become A Tester. Click on that and then you are good to go.
The solution in my case was to select the app in the Google Play Console, then go to Release > Production > Countries/regions, and add the countries/regions there. Having the countries/regions selected in the closed/internal track only is not sufficient. It seems this is necessary regardless of whether one actually has a production release or not - again, in my case, I did not. It took maybe 10-20 mins after I made the update until I stopped seeing the issue.
TL;DR:
Upload to the Internal Test track and make sure it has the highest version code
I was having this issue for a few days, and also tried numerous things, but to no avail.. I uploaded my app bundle to a Closed Testing track in the Play Store, which did not solve the problem. After countless other methods, I eventually tried to upload a bundle to the Internal Testing track, which immediately solved the issue and allowed me to use test cards again.
I've created a device owner app, which I install through a QR code when I factory reset my devices. Everything's fine until here.
Now I have a new version of the same device owner app, and I want to update the devices which have the previous version to this new version.
Is it possible to achieve this using Google Play?
I don't want to use custom methods like uploading the APK somewhere and downloading it with some Java code, because I want to centralize the releases in Google Play.
So far I have uploaded the new version (version code is 5, old one is 2) of the app to Google Play and tried to upgrade from there, but it does not work: in Google Play I just see the app as installed, and the "Disable" and "Open" button, but not the button to upgrade it.
Any thoughts? I've found some posts like the ones below, but they're 5 years old, maybe something has changed and this is not longer possible.
Install updates for a Device-Owner App
Install a GooglePlay located App from NFC
I haven't been able to find any specific information on updates with device owner apps. The documentation is extensive about how to create and install a device owner app, but not on how to upgrade it.
Thanks a lot in advance!
You didn't install it from play store , I THINK you can't update Device-Owner apps which were not installed from play store , except for the way you mentioned.
We implemented some time ago In App Updates using Google Play Core library, and recently (started on September 8th) to shown on our Crashlytics lots of Install Error (-100) crashes.
Not sure if Google Play rollout something on that day, but even after we update the library to version 1.8.0 (before it was 1.7.3), the crashes continue reaching up to 7% of our daily active users.
Following the stacktrace of the crash:
Caused by com.google.android.play.core.install.InstallException: Install Error(-100): An internal error happened in the Play Store. (https://developer.android.com/reference/com/google/android/play/core/install/model/InstallErrorCode#ERROR_INTERNAL_ERROR)
at com.google.android.play.core.appupdate.o.a(o.java:6)
at com.google.android.play.core.internal.o.a(o.java:28)
at com.google.android.play.core.internal.j.onTransact(j.java:20)
at android.os.Binder.execTransactInternal(Binder.java:1056)
at android.os.Binder.execTransact(Binder.java:1029)
The question is what is this error? Internal Error seems to be a generic one, which doesn't say much about how can I fix it.
It seems to be a duplicated of this one, but as there is no answer to it I'm asking again.
How to solve install status code -100 while working with In-App update in Android?
I have solution!
For testing you app you mast to upload two versions of apk to the Enternal app sharing.
First version - for example version code 1, the second version - version code 2.
Nexn step - You need to get the first app link from enternal app storage and follow this link, install this apk on your smartphone.
Next - follow on link of the second app, but dont press any button on opened screen, just close market screen. 3. Step three - open the first app and try to update by following your update steps logic in your app.
I have a problem in an app updated in play store.
Around 800 user could updated it without problem, but we have 3 users who get this message:
I've try install it with apk instead play store, with a similar result:
The min SDK is 16 and the SDK target is 28, and this devices have SDK 27 and 28.
One of these users had a device in which she couldn't install it. But last week buy new device, and she can't install it too. This new device has never had the application installed before.
How can I see any information about the problem?
I had such a problem, when tried to install a new version of my app. I found the reason for the problem when installing the new release version of my app using Android Studio. The error message has explained in detail what the problem is.
So if someone has such a problem I would suggest getting a device on which the error can be reproduced, then trying to install it using Android Studio and check the message.
The full story in my case was as the following: I had two different applicationId for "release" and "debug" configurations. In the new version of the app, I added a "provider" to the manifest. During my development I installed the debug version and then I deployed the new version to the Play Store. When I tried to install the deployed app on this device I got the message that it cannot be installed. The reason was that the release version had the same provider as the debug version, so they cannot be installed both. The solution is to change the authorities of the provider according to the applicationId.
This looks like a problem on the device, rather than a problem downloading from Google Play store. Logs from this should be in the users device logs, like you get for your app. You can ask your user for the logs, by asking them to send you a bug report. There are instructions here on taking bug reports.
When you look at the bug report, error messages from the Play store are tagged with "Finsky". You may also see errors from the device package manager.
When errors like this occured, it is recommended to read the link (see common ways to fix the problem). Most of the time cleaning Google Play Services cache and data will do the trick:
Clear the Google Play Store cache
1.Open the Settings menu on your device.
2.Go to Apps or Application Manager. (This option might differ depending on your device.)
3.Scroll to All apps and then scroll down to the Google Play Store app.
4.Open the app details and tap the Force stop button.
5.Tap the Clear cache button.
Repeat the steps above, but replace Google Play Store in step 3 with Google Play services.
Try to download the app again.
Clear the Google Play Store data
If cleaning the cache of the Google Play Store and Google Play Services doesn't resolve the issue, try clearing the Google Play Store data:
1.Open the Settings menu on your device.
2.Go to Apps or Application Manager. (This option might differ depending on your device.)
3.Scroll to All apps and then scroll down to the Google Play Store app.
4.Open the app details and tap the Force stop button.
5.Tap the Clear data button.
6.Clear data button
We have an Application which utilizes In App Billing. The problem that we're seeing is as follows:
When the versionCode of the App on the device is the same as the version code of the Application published in the Play Developer Console, Billing works fine.
When a build with a higher versionCode is uploaded to the Play Developer Console, In App Billing stops working on the App on the device (with a lower versionCode) saying that "The Application is not configured for Billing".
This is fine, when testing, but the question is - what is the behavior when the App is in the Google Play Store? When you replace the Application (to perform an update) does the Application that's in the wild (with a lower versionCode) stop working with In App Billing?
If so, what approach do people use to performing updates? Do you force the user to update before purchasing? Or is this problem only true prior to publishing?
Any advice would be greatly appreciated!
Thanks!
As long as the "newer" apk that you upload is signed using the same key as the existing one then you shouldn't run into any problems.
I have just tested running my app with a previous version (version code is lower) and in app billing still works.
The caveat is that you must not delete the apk from the market, simply deactivate it.
But what you say about forcing updates, I do prompt the user to update when they open the app regardless.
You may have already read it, but here is the official info on multiple apks.