I distributed an apk using "yyMMddhhmm" as versionCode. Now I realized that maximum version code is 2100000000 and so I can't upload any upgrade: I have a millenium bug on 2021!
How can I get around?
If I remove previous version, users will receive the new one?
Thank you.
Android only updates to higher versionCodes, so you can only go higher and never lower. Play Console enforces this but this is a restriction of Android in the first place.
The only option you have is contact the Play Developer support and ask them if they can allow you to publish versions that go all the way to 2,147,483,647 which is theoretically the highest versionCode you can have today.
Obviously, you'll have to adjust your allocation of versionCodes and be more frugal onwards in how you consume them.
Related
Can we release an app update in Google Play dev console to 99% of users, and then reduce it to 50%?
I know about halt option, but that's not the same and we're interested specifically in decreasing % of new installs that'll receive the new version.
Thanks.
According to the Android Wear Developer Training guide for Wear 2.0 Watch Face Complications, though the developer can, via the manifest file, define a set interval where a complication provider can request an update, there is the caveat that "update requests are not guaranteed to be sent with this frequency" and that "the system does apply a minimum update period, and in particular, update requests may come less often when the device is in ambient mode or is not worn."
Is there any documentation or source specifying exactly what this minimum update period is, or how it is derived?
UPDATE: The reason that I am asking this is that our organization is looking to develop an application that will both run on Apple Watch and Android Wear, and it was noted by the Apple Watch side of development that the Apple Watch OS only permits 50 updates to their complications for every 24 hour time period; the project manager for this application is very curious if the Android Wear 2.0 OS has any similar restrictions, or if a developer is, in theory, capable of updating complications "freely" (i.e. without consideration of the end user's device's battery).
As I've read the documentation you linked, it didn't state the minimum update period you can specify. However, based from this example, developers should consider intervals in the order of minutes. Also, remember that this is only a guidance for the system. Android Wear may update less frequently. Unfortunately, I cannot also see any documentation regarding the exact time to specify but this value should be set as large as possible, to not have a too big impact on the device battery, due to frequent updates. You can check this blog. But if your app needs to push updates instead of updating on a regular schedule, you should set this value to 0 and use ProviderUpdateRequester.requestUpdate() instead to trigger an update request when you need one.
When developing online game I would really like to avoid supporting different protocol versions. The server can check the version of a client and deny login until the client gets updated. But the problem here is that I need the app update to become available simultanously at the same time on AppStore and Google Play.
Is it possible to do? How do you solve such versioning problems?
Well, I am not sure how it works for the GooglePlayStore but if you choose Developer Release instead of automatic then you could just release it in the moment it approves on the GooglePlayStore and about 30mins. later your iOS app will be online and available as well. That's what I'd do.
Google Play Developer Console allows developers to upload a beta APK, and invite a Google Group to use it.
How to know how many users are using my beta?
In the console:
Go to Statistics,
Click Export as CSV,
Uncheck everything but Installs devices current and by app version
In the resulting CSV, spot the id of the APK you sent for beta
The number in the third column is the number of beta users.
The Google Play Developer Console has changed a lot since the original answer.
If you are using Open Beta Testing then go to:
Release Management / App Releases / Manage Beta
and you will see something like this:
Note: if the number of testers is not showing, this might be because the number has not yet reached a certain threshold.
This specifically answers the question "How many people have opted into Beta testing?" which may or may not be what the OP was really interested in.
Analytics would be the way to discover how many are actually using the beta version.
Xcode 4.0.1 was released a few days ago, which means that I am once again downloading the 4.5 GB beast to update. Does anyone know if Apple plans to introduce a better update system?
I wait for a torrent these days. Not quite as frustrating as getting it 80% of the way downloaded and losing connection.
If you are registered apple user then u can download directly from apple site,otherwise you need to get it from torrent. like www.thepiratebay.org etc
Since 4.3 the whole Xcode toolchain is bundled into a single Mac App Store application. The Mac App Store supports delta updates and the update to 4.3.1 that I’m downloading right now is ~900M, compared to ~1.5G for the whole app. So it looks like the update sizes are finally coming down, if slowly.