I have published my first release of android APP on Google Play console, Its not approved yet (Still In Review for 5 days now).
I found that the app has an error and will crash on start.
I want to discard the first release and publish the new one which contains the fixes.
I think my app still in review for 5 days now because it crashes and I want to fix it but don't know how.
If I try to publish a new release on Google Play, it says "You cannot remove all production APKs and Android App Bundles"
Any Help
I have actually uploaded an update version of an app before its first release was approved and published. (The reason was I forgot obfuscation...) It was approved and published later without problem.
But I can't understand your saying:
If I try to publish a new release on Google Play, it says "You cannot
remove all production APKs and Android App Bundles"
If you tried just uploading an update version, I can't understand why it led to remove all production.
If you didn't just upload an update version but you tried to remove or something, you might doing something wrong. But you didn't disclose detail about that, nothing could suggest anymore.
I think you just exit upload window. Find button "сontinue uploading" in versions section and upload yours's new version of application.
Related
I couldn't find any similar topic in here or google. I uploaded an app in play store and then I uploaded a new version of it. But now, It always asks for an update in market. I don't know is it due to my code or something. When I upload an update I increase the versionCode and rename the versionName in android studio then sign it
Then I go to play console - select the app - release management - release dashboard
Then I release my new version. I select "Android App Bundles and APKs to deactivate". I don't click "retain" It seems like a stupid post but I don't know what the problem is. I did it before I've never faced such an issue. I do everything like described in here https://customersupport.doubledutch.me/hc/en-us/articles/360001395033-Android-How-to-Update-an-App-in-the-Google-Play-Developer-Console
Finally it always asks for update in the market
I would be glad for any tiny idea. If stackoverflow is not the correct place for this post can you at least redirect me the correct place? Thanks.
I have been trying for several weeks now to get the Google Alpha / Beta testing functionality on the Play Store to work with no success. As far as I can tell I have followed the process but clearly something is not working from my side. I hope someone on SO can tell me what I'm doing wrong.
I have created both an Apha and Beta testing community.
I have added the Beta testing community to the Beta testing section that relates to using Google+ communities to test. My Beta testing community does have members added.
Although I have an Alpha testing community, none of the Alpha testing methods are currently enabled.
On my test device, using a Google account that is a member of my Beta testing community, I only ever see the version of my app that is currently in Prod. I have spent days waiting just in case it takes a couple of days to show up (at least a week which I assume should be long enough).
I need to test the release version because I am trying to test some inapp billing functionality that I had to change due to security warnings from Google relating to my current Prod version.
BUT: if I load the release version of the app directly (instead of downloading from the Play Store) I can see that it is seeing this account as a "test account" because when I test the inapp billing I get the correct message telling me that the subscription will renew every day but I won't be charged. However the Beta version of the app never appears in the "BETA" tab in the Play Store.
I have noticed something "strange" (possibly) in the developer console though: When I click on the "Beta Testing" tab it shows 10399 supported devices and 0 excluded devices for the Beta app. However if I click on the line of the Beta app where you can promote the app etc, the details that are then displayed indicate 0 supported Android devices. Why would this be? This seems to be conflicting information on the console.
Note: The current Prod version of my app was developed using Eclipse. I have recently converted to Android Studio and this is my first upload using Android Studio.
Where else should I be looking to get my app to appear in the Play Store
Thanks
I was just setting up the Beta testing release for the first time and couldn't make the app visible in Play Store. Found the reason in Play Console Help:
After publishing an alpha/beta app for the first time, it may take a few hours for your test link to be available to testers. If you publish additional changes, they may take several hours to be available for testers.
After about 35 minutes the app was published.
As this might not be the issue mentioned in original question, it might help someone.
In my case I had published the Beta version and had created the testers but not linked them together. What I had to do was:
Go to manage releases
Choose a testing method - Closed Beta Testing
Then when testers list shows, make active the group of testers you would like to test the app.
Save
Get Opt-in URL link and paste it in a new tab (you should be logged in to google)
Then click at the "Become a Tester" button
You should now be a tester and ready to go.
#Important If you still can not find the app by searching in Play Store just copy the "Opt-in URL" into your tester phone's browser and you should see the app.
Hope it helps
What solved this problem for me was clearing my Play Store app data.
In my case, I had already been on the testers list for days, already accepted the invitation link, and already gotten testing working on other devices. But, the Play Store still wouldn't show the beta version of the app on this particular device.
I went to "App info" for the Google Play Store app, "Memory", then "Clear data". Then I re-opened and was able to see the beta test app.
Disclaimer: Use with caution. Clearing your app data may remove some important information. I haven't personally experienced any problems with it, but that doesn't mean you won't.
The suggestion from #Edgehog to use Open Testing solved my problem regarding being able to see my app in the Beta tab of the Play Store.
I have not found a reason yet why the closed beta testing (using emails or groups/communities) would not work.
Make sure you also check this answer
browser cache
an actual active "testing track"
We are having the same problem in my company. Currently we are investigating possibility that maybe first install on beta channel installs prod version and updates to beta channel version when first app update is released on beta channel. It is weird workflow but the comment on Play Store "Future updates will include beta versions" supports this
There are a couple of reasons why this might happen but admittedly we did not 100% confirm this.
1) One reason is that you are viewing Google Play under another account that is not on the beta tester list.
2) The other might be an issue (or feature) with the release management. Added a user to an existing closed beta release list. Changing a list does not activate or force a Save for the "Managed testers" section. After we edited another field (e.g. feedback channel) then the Save button became active and we clicked save. This might only then propagate changes. We cannot 100% confirm this was the issue we were facing but our experience points to this.
I'm trying to add an application for beta testing for first time. I made a mistake and instead of adding it on beta tab I did it on production one.
I'm trying to cancel the publish process but I'm not able to do so.
I've switched to advanced mode and clicked "deactivate" but I get the following error
This configuration cannot be published for the following reason(s):
You must have at least one active APK.
I don't want to publish the App. This other question Unable to deactivate APK accidentally uploaded to Prod seems to indicate that there is no possibility to revert this mistake. How is that posible?????
EDIT
It seems I'll be able to unpublish this app. Is it possible to publish it again later using the same package id and just change the version?
No, you can unpublish but once your application has been live on the market you cannot delete it.Only older version can be deleted
You cannot cancel the publishing, at least I think that if you upload a beta apk with higher version name it replaces the active app.
The error I think it's because the app is not published yet it takes around 2 hours to publish.
If this question I'm about to ask was already asked, please just direct me to the link as I didn't find it. For the beta testing in google play, do you have to first un-publish a beta APK before the new one will take its place? Also can you upload the same version code or do you have to create a new version code with each APK upload in Beta?
The reason I ask is I was about to Beta test a new version of an application. I upgraded the application on my test phone and it crashed. I found out there was a line of code I forgot to take out for testing purposes which caused the upgrade to break. Which is funny because the testing code was testing, indirectly, the upgrade code. Anyway, so I didn't want to upload a whole new code version just overwrite the pre-existing APK upload. I was hoping this was possible due to it only being in Beta status. Also, I guess this means having to potentially wait another 24 hours for his new Beta APK upload to take effect. That was another thing I was hoping to bypass was uploading the same version in Beta would wipe out the pre-existing Beta version code so the changes would be immediately upgradable. Wishful thinking I'm assuming.
Thank You in advance.
No, you do not have to un-publish your application to upload a new Beta version. However, you must increment the version code in order to release a new Beta version. The version code must be incremented, so devices that installed your application can track whether an update is available, by comparing the installed version code to the Google Play version code.
Every time you release a new version or update your application info, it could take a few hours for these changes to propagate. In my experience, it only takes about 5 hours until people start receiving the update notification. If you are really bothered by the time it takes for new versions to be available, you could use a different app distribution service, for example HockeyApp, TestFlight, etc...
When your app is ready to production, you don´t have to unpublish, just "promote to production", you don´t have to change the versionCode.
If your Beta application has bugs, made the changes and you have to upload another .apk and yes, you have to change to the newer versionCode.
If your app was published, you can´t overwrite the pre-existing APK.
I have some questions related to updating an android app on Google Play, that I seem to find the answer nowhere. I updated an app, and after aprox an hour, I noticed a problem with that new apk, so I had to create a newer update. I read on Google Docs that an update would take up to 24 hours to be surelly released to users, so if I will update it again, would that be a problem? Will the users see only the last update? Can I deactivate an update and let only the last one to be released? I appreciate any answers!
If you notice a problem in just released version, you can deactivate it and activate the previous version (you can do that in advanced mode). Some users may get the new release in the meantime though.
You can later release a new version and users will then see this new version as the upgrade.
just sign your new apk with old keystore and got o console old app console and in you may/maynot unpublish your old version.just add new apk to production and it will update in 2-3 hours.