I have not updated my Android app for quite a while. Now I would like to use the Alpha Test to run some tests of the In-App Purchase features.
Problem is, that I do not see how I can install the Alpha version on my device using the Play Store. I did the following:
Android Studio 2.1
APK/Alpha-Test
I uploaded/published the alpha APK on three days ago. Even if it can take some hours before an update reaches the store, three days should be long enough, shouldn't it?
I found other threads dealing with this kind of problem and in some cases the solution was to clean the cache of the Play Store App and restart the app. However this did not change anything in my case.
So, none of the suggested solutions I found worked for me. Any other idea what I can do?
UPDATE:
Still not possible to update to the alpha version. I now switch from a Closed Alpha Test an Alpha Test using a Google+ Community. However, the result is the same:
Published the changes.
When visiting the test URL (https://play.google.com/apps/testing/com.mycompany.myapp) I got the message "You are not a tester"
UPDATE 2:
Also after switching to a Public Alpha Test still no update available.
I am running out of ideas...
The Google Play Store can stop working or start showing unresponsive behaviors. The reason could be either the service is down, or could be an OS or app-specific issue. Clearing cache, restarting device or updating app are some of the common fixes to resolve the issue.
You just need to register their Google ID in the list of testers, and then share the download link of your app with them, and then they will be able to access (download) the app on their Android device.
After two weeks I was finally able to solve the issue. I share the solution here, just in case somebody encounters the same type of problem:
I contacted Google Support to find out, if there is any known problem that prevents the test version from beeing downloaded. They told me, that the uploaded APK was not compatible with my test device (Nexus 5) due to an incompatible ABI version.
This was quite confusing, sinc my app did not use any native code and thus did not configure any ABI version at all.
Finally Google told me, that the ABI
version of the APK was identified as commons-io-2.4.jar
. This still does not make sense, since this is obviously not an ABI version. However with this information I was able to move on and find a way to avoid the problem.
Android Stuido copied the commons-io-2.4.jar
file into the lib
folder within the APK. The Dev Console identified the content of this folder as ABI
version (which does not make any sense) and thus the APK was marked as not compatible with the device.
Either there is a bug in Android Studio (copied the file into the lib folder) or the Dev Console (identifies the lib content als ABI version).
SOLUTION
Since I did not need the commons-io-2.4.jar anymore, I could simply remove it from the project and the new version is distributed without any problem in the Alpha/Beta Test Channel. I have no idea what I would have done, if the app would depend on this lib.
The information in the Dev Console on wether an APK is supported by specific devices or not is quite confusing:
The public version of the APK was (of course) compatible to thousands of different devices, including the Nexus 5 I use for my test. The Dev Console shows the same information (the one of the public APK) for the test APK as well. Thus I assumed, that the test APK is correct and compatible. One can only see the information about the test APK, by clicking on the APK in the Dev Console.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With