I'm trying to beta test an sdk that I uploaded to the developer console 2 days ago.
I have an apk currently published on production and a newer apk published in beta.
I followed all the steps (created google+ group, added testers, etc) but when I get to the https://play.google.com/apps/testing/***** page, it send me to the production app to download with an older version number.
So basically, I cannot download the beta apk from the play store, it makes me download the production version.
Has anyone ever had a similar experience? I'm trying to test out in-app purchases, but this is really putting a damper on my progress... any help is greatly appreciated!
Thanks!
In case anyone has the same question I did, the answer was simply to wait.
Related
I have this app released on play store that I want to make available on my website. I tried downloading the signed apk via the Google play console and use that, but some users in China have issues installing it.
They get a message like this while installing: "Your device does not support Google Play Services and cannot install "
I have a few Google sdk bits referenced in my project (signin, safetyNet, ads) which I would assume I need to delete before building for this apk version, since target devices don't have gms..
What about signing? Can I simply build without the said code and distribute it? (Generate release apk in android studio) Or do I need to upload to play console and download the one signed from google?
Please let me know if you have any clues on this, been banging my head around for a few days already.
Cheers :)
This might help you taking your decision:
If you have Play App Signing enabled, the APK generated through your studio and the APK generated through Play Console will have different signatures.
Otherwise, both approaches will have the same signatures.
So, it depends whether you care about your APK on website having the same signature as Play Store. If you don't care about having same signature, you can go ahead with creating APK from Android Studio itself and publish to your website.
If your app utilizes Google Play Services, as is informed by the error message, then it WILL not run on the device unless Google Play Services and everything that it depends on is installed on the device. The only work around is to convert your app features that uses Google Play Services to its alternative that's supported in China.
I've dealt with similar issue on Huawei smartphones, my approach was to 'develop another app' using Huawei SDK, check out https://developer.huawei.com/consumer/en/ for its complete reference
I have 4 signed release build apks of different architectures (35.MB on average is size) and had submitted for Alpha and Beta testing. While as a tester I downloaded the app from Google Play Store, but it was showing up 111 MB file while I was downloading it.
I thought it was how it worked for Alpha and Beta, but while I move the same release to production I faced the same issue. Now the app is on production but I am worried the users may not panic for 111 MB app which was earlier as 35.40 MB on average for all devices. Refer screens below.
Earlier I never posted the builds for Alpha and Beta testing, but this time there was a requirement for Upgrade activity.
This one shows up in one of the apk release details:
Info for the the same build:
This SO post could be the answer.
If that is a paid application, you may implement the Google Play licensing service, else (if free), implement your own copy protection scheme.
You may check this github post for more related issue.
Hope this helps.
I have a production version and a beta version of my app. I'm one of my beta testers. I want to rollback the version on my phone to the production version so that I can configure some settings then reinstall the beta to ensure the upgrade is working properly.
I can't seem to figure out how to re-install the production version though. I've even tried leaving the beta test and I can't get Google Play to notice that I'm not a beta tester anymore. (deleted cache and data, rebooted phone, etc).
With iOS I can install the production version from the App Store and the test version from Test Flight. How do I do that on Android?
Use different account (new google account) from Google Play to download production, then enroll in beta and try to update. this is the quickest way.
Note: you probably facing this problem because you are an internal tester and a closed beta tester too.
Toggling Developer settings helps to install the production and then switching developer settings back on gives the option to update to beta once again.
EDIT: Actually this helps only to get the change to reflect if test track is paused or resumed
Found the fix here https://android.stackexchange.com/a/245371/374079
I already had a version (versioncode=2) in Google Store. Yesterday after doing some changes, when I tried publishing the app, i am getting below error message and not able to publish the updates. Any idea how can I fix it?
This configuration cannot be published for the following reason(s):
Version 2 is not served to any device configuration: all devices that might receive version 2 would receive version 3.
Some devices are eligible to run multiple APKs. In such a scenario, the device will receive the APK with the higher version code.
FYI, the new version is versioncode=3
You need to "Deactivate" the current apk in order to actually publish the new apk.
Deactivate the 2 version on the Google Play.
All this says is that version 3 is applicable for all devices that version 2 is applicable for. This means version 2 is obsolete.
If you check closely, when you upload your APK there is no option to Publish to production, only Save as Draft. This happened to me last night and drove me crazy. Now, in the morning I uploaded the new APK again and the Publish to production button was there! I don't what caused this issue but now it's fine.
I've been distributing beta APKs to my testers with the LVL checking enabled, and I'm getting many reports of the app behaving as if it is not licensed.
This is not a problem in the current version that is in the Play Store, and the LVL checking code hasn't changed since my last release.
I'm wondering: will the LVL library return 'unlicensed' or behave unpredictably on APKs that have not yet been uploaded to the Android Developer Console? Is it possibly these problems will go away when this update is downloaded from the Play Store?
I ended up pushing my update live, and I've not had any reports of the licensing failing with this code.
As was suggested in this thread, commenting out the versionCode/mVersionCode check in LicenseValidator was likely the reason my beta APK was failing. Hope that helps someone.