I need help for removing the beta app submitted in google play store, Recently I have submitted my app with Targeted SDK version 23 for beta testing but now I want to submit the app with targeted SDK version 15 for production.
I have tried by submitting the App to Production with targeted SDK version 15 but it showed me an error saying:
Permission model downgrade PROBLEM: Users that have the APK version
code XXXX1, which targets SDK 23 or higher, will receive an error when
they attempt to upgrade to this apk XXXX2 because it targets SDK 15.
Is there any way to delete the existing beta app or to submit the production app with SDK15 other than un-publishing the app? Un-publishing the app will cause the inconvenience to existing users.
There is no way to delete a build from the Alpha or Beta channels. What you have to do is, deploy an artifact with a higher build code to the channel, then promote the channel to production. The APK that you want to remove will not show up, only the build with the highest build code, so there is no risk to doing this.
(source - just worked with Google Play support on a similar issue.)
Related
I have an Android App on playstore. Now I have made so many changes to this app and want to update my app. I know simple update is easy but the thing I want is that to publish the new version in beta by keeping the old version remains same. In simple word, I want to publish a new build with beta version that it don't effect the older version?
Note: Old version is not in beta.
Releasing app update to beta channel (open testing) doesn't remove the production release. The beta update will become available as an update to testers only, everyone else will have access to the production release.
For more on releases and roll-outs. Read more here
My company has an Android app published on the Play Store since 2018. We never had any problem with the app's distribution, however since July 2020 new versions submitted and released with full rollout do not appear on the Play Store's web page or Android app - they only show an older version, published on June 2020.
We are sure that this is not a matter of caching on our end, as it is consistent across devices and platforms.
Initially, we noted that the Pre-launch report page of the Developer Console showed a few errors for these newer builds and thought that because of them the system would not release the updates, so we fixed the errors. It didn't work.
We also used to use fastlane for preparing the app's APK and uploading it, so we tried preparing the APK using Android Studio's Generate Signed APK option and uploading it manually. It also didn't work.
Our app deals with mature themes (partner swapping), but we take very good care for it to be as safe as possible. The Google Play's Developer Console shows no warning or error message for the app, so we doubt this could be the reason.
New beta and internal versions appear to beta and internal testers, but when upgraded to production, they go back to the old version from June.
No changes were made to minSdkVersion or targetSdkVersion.
I have an app in open beta release in Google playstore. I am able to download the beta app for android version 7+ but in android 6 devices even when I have the beta access I end up downloading only the previous production release app.
NOTE: Min Sdk for my app in Gradle file is 23 in production build and 21 in beta version. Version code of the app has been incremented over the previous version.
Is there anyone who has faced same/similar issue and if so how did you resolve it?
Edit 1 :
When I download the app in android 6 device I am ablke to see the (Beta) next to app name and the beta column in my app list menu , but when I open the app then it turns out to be the production build only.
I'm working on an app which is in Beta (no released version in production yet).
I've uploaded a new APK yesterday. When doing that I got a warning as I changed the minSdkVersion from 16 to 19. I made this change on purpose so it was expected.
On the Google Play Console, it now shows that a new APK has been added and the old one has be deactivated, which is what I want.
However, the Play Store now display 'Varies with device' under the 'Requires Android' section of the app information.
So it seems the Store has kept the old version for the people having Android between API 16 and 19, like if I wanted Multiple APK.
How to solve this issue?
EDIT
I've released a new Alpha version to get rid of the old one which was still there and 'shadowed' by the Beta (this Alpha supported Android from API 16), and then promoted it to Beta. So now I have no Alpha, still no app in production, and only one Beta APK with minSdkVersion set to 19.
This Beta is now displayed on the Store page, however both 'Requires Android' and Current version still display 'Varies with device'.
After contacting Google support, here is their answer:
I looked into your matter further and the reason why you can see the
'Varies with device' under 'Requires Android' is because the app is
unreleased.
Please note that if the app is published then the section for
'Requires Android' will be updated with the relevant information.
So I'll see if the values are correctly updated when I'll release the app.
I am getting the following error when trying to publish a new APK in Google Play:
It is forbidden to downgrade devices which previously used M permissions (target SDK 23 and above) to APKs which use old style permissions (target SDK 22 and below). This occurs in the change from version 2645 (target SDK 23) to version 2648 (target SDK 11).
I previously published only on Beta channel an APK with a target SDK of 23 in the manifest, just for testing.
I assume this is what causing the issue.
Does this mean I can't ever publish another APK with my regular manifest, which has a lower target SDK?
Did anyone encounter this and know of a way around it?
i want to show you something. hope you understand!
I've hit the same thing. I'm stuck on Marshmallow because I upgraded my target SDK in Beta.
One would think that you can back out as far as you want on a beta or alpha channel as long as it has not been published to production. That is the way it would work in the real world.
You only have a hind-site workaround.
The workaround is to not to develop for Marshmallow in Beta on your production app. Create a new application in Google Play and develop there until it is ready. This will also let you update the production code if a bug fix comes up before your marshmallow release.