I am not happy with the current version of my app in the Play Store. I would like to disable it (for now).
Q: If I disable it, are the users who already upgraded to the new version eventually downgraded to the older (re-activated) version?
No, they stay on the last published version as far as I'm aware. People who have installed the version you are not happy with will keep having it even after you deactivate.
There is no downgrade or "revert to previous" process.
If you're unhappy, best thing to do if possible it to post an update/fixed version before you deactivate.
Edit: Can't find any official info but found someone else who agrees (https://stackoverflow.com/a/13493065/833647).
I speak from experience of doing exactly what you describe :)
Related
DISCLAIMER
I'm opening this Q&A because:
I've tried contacting OneLogin through Twitter without success
I can't fill a bug without a Developer Account (which I don't want)
They clearly state in their site to ask on Stackoverflow when seeing weird errors:
THE PROBLEM
In my company, we're using the OneLogin Protect as 2FA (OTP) device for accessing a partner VPN.
On December 10, 2019, OneLogin released the version 4.3.0 of its app, which our smartphones automatically updated from the previous 4.1.0, which was fully working.
The 4.3.0 app crashes when starting, with a miserable NPE:
THE ATTEMPTS AND THE QUESTIONS
I've reinstalled it, reinstalled the previous version (which got updated again), disabled the automatic updates (which is not something I'm happy about), but this is so fragile, so I'm asking:
Is this happening to us only, or it's a huge production bug?
Is there any way to fix it?
Are you guys at OneLogin aware of this? Are you working on it? Have you a release date for a patched version?
Hint: the problem is in the Kotlin file Utils.kt, row 42. Sanitize the input, for God sake
The bug has been found and fixed and a new version has been posted to the Play Store. If you update, look for version 4.3 (187) or higher.
As the title says, we published a new version of an app 2 weeks ago. Play Store indicates in the registry that the new version was uploaded (1.7), and allows it to be downloaded to users who did not have it. Not so, for those who already have it, for example, users who have version 1.6, do not see the option to update, just uninstall or open.
We expected it to be only a matter of time, but 2 weeks is already too much. We contacted Google support, and they only ask us questions like: "Have automatic updates for the application enabled?" ... Does anyone know what is happening, or if it is our mistake, some step wrongly made? We generate the apk directly from Android Studio and change the version.
One of the issues that your users might have is this
Maybe they disabled the auto-updates of Google Play, but is really weird that they can't see it, maybe it's due the devices. Is your device listed as compatible with the new version of your app? Did you tried clearing Google Play cache and trying it again?
PS: Make sure you change in your Gradle (Module app) your versionCode along with the VersionName
If new users are getting the new version installed then it is definitely uploaded to the Play store correctly.
If existing users aren't seeing "update" (just open) then it means there is something about the new version of the app that is incompatible with their devices. You can check this by trying uninstalling and re-installing. If they get the old version after an uninstall / re-install (or worse, if they can't install after uninstalling) it shows that only the old version is compatible with their device.
This probably means you changed something in the manifest to make it incompatible, but that is a whole different debugging problem.
Just upgraded an app from V12 to V13 - text change in help only. Works fine.
Go up upload it to dev. console and it will not publish the new APK, says:
"This configuration cannot be published for the following reason(s):
Version 12 is not served to any device configuration: all devices that might receive version 12 would receive version 13."
What is it talking about? V12 was published for 40K+ devices, I've just done exactly the same thing to three other apps with no problem, but this one won't have it.
No idea what it means. All I can do is save it as draft.
I think it is known problem of Google developer console.
Please see this answer
When you upload a new version of an app, you need to manually deactivate the previous version, until you do, the dev console won't let you publish the new state.
Both answers above equally good. I had tried the second one and it didn't work. Went back a few hours later, still didn't work, did the second answer again, and it did. Very strange ....
thankfully I don't think I have a problem with my app, but the chance of this issue made me want to ask the question on SO.
Scenario: Assuming many folk have automatic updating set against my app (as I do), what would happen if I launched an update that percolated through the market, only to find that I had cocked-up something major and needed time to fix. My first action would be to deactivate the newest version, and activate the next older version.
Question: What would happen on the phone if they have the newer version? Would it automatically update to the older 'live' version?
And yes, I know I should test, test, test so that I never get in this position...;-)
Thanks
No, downgrade won't work, yet, by unpublishing faulty app you prevent those who did not upgrade yet from facing problems, but those who already upgraded can simply uninstall the app and install it again, thus revering to last stable version. Market will not downgrade installed apps. It only works for updates (comparing versionCodes)
SoundPool has a serious bug in it in Android 1.5. I fixed it with a workaround, but since it really limits my app, I want to target 1.6+ for the next version of it.
I am wondering: What happens when I release a upgrade that has a higher target SDK version then the previous version of my app? Will only 1.6+ users be able to upgrade their app? Or will also the 1.5 users be able to upgrade since they have the program already installed?
Anybody experience with this?
Since you answered one of my questions, I thought I'd take a look at your questions:-
From what I've read on the Android dev site:-
The manifest holds the MINIMUM version that the APK will support. Only users with the same version or higher of that SDK will be able to even see you App in the Market.
Therefore, to answer your question, YES, only users with OS 1.6+ Android will be able to upgrade. I released an app once, set to 1.6, and wondered why I was getting less downloads, then realised what I had done, set it back to 1.5, and all was well.
Is there anyway you could get the newer 1.6 source for soundpool, add that to your app, and use it when version 1.5 is detected (or, just use it all the time).
Lots of hassle I know, but just a thought.
Havn't got any experience with this but that a 1.5 user can use an app targeted for minimum 1.6 seems highly unlikely. They will probably be informed that your app no longer supports their platform or just not recive the update.