Update your apps
Prepare your APK
When you are ready to make modifications to your APK,
also update the app version code for users to receive
this update.
Use the following checklist to check if the new APK is
ready to update existing users:
- The updated APK package name needs to be the same as the version
current.
- The version code needs to be higher than the current version.
Learn more about the version control of your apps.
- The updated APK needs to be tagged with the same subscription as the current version.
To check if your APK is using the same version certification
previous, it is possible to execute the following command on both Apks and
compare the results:
$ jarsigner -verify -verbose -certs my_application.apk
If the results are identical, it means you use the same
key and is ready to continue. If the results are different,
you will need to sign the APK again with the correct key.
Upload to your APK
Once your APK is ready, it will be possible create a new version.
Delivery of updates
After sending an update to an app, you’ll see "Update pending" in the upper-right corner of the app’s Play Console pages. Once the update is published, it will begin to be distributed to existing users.
When the update is available, users will be able to do
download it on the "App Details" page or on the page My apps of
Play Store app. If a user has enabled automatic app updates, the update will be automatically downloaded and installed.
App updates take some time to reach users
existing. If you have submitted an update that has not yet
appeared on Google Play, wait at least 24 hours before
contact our support team.
Update apps from the system
Users will see the system apps (including pre-loaded apps)
in the My Apps section of the Google Play Store as soon as an app has the same
package name is sent to the Play Console (even if the app does not
has been published).
Google Play can manage pre-loaded app updates, a
as the following conditions are met:
The preloaded application needs to be on the system partition
The pre-loaded app needs to be free
The pre-loaded app needs to have the same app subscription posted on Google Play
The package name of the pre-loaded app and the updated app needs to be the same
The updated app version code needs to be higher than the pre-loaded one
Very difficult to know what happened with only this information :/
– Guilherme Nascimento
but what other things could it be? type what are the main mistakes that cause this rejection?
– Rudda Beltrao
Put what you did, what you changed. You reinstalled something, it gets very broad to answer like that and if it’s something very broad then the question is outside the accepted scope of the site, you know? Try to give details.
– Guilherme Nascimento
am virtually on the same error as https://answall.com/questions/267005/update-apk-google-play-apk-n%C3%A3o-actuaz%C3%A1vel
– Rudda Beltrao
And you realize you didn’t get any answers either, right? This occurs for lack of details, its final problem may be equal to yours, but the origin of the problem may be totally different, only that both and different failures have caused the same problem.
– Guilherme Nascimento
See if this resolves https://answall.com/a/235268/3635
– Guilherme Nascimento
I’ve already changed it, it just pops up this message. Maybe it’s architecture? Because the tip tells me to make sure that all the apks are added to the version, what does that mean? I cannot know the error simply with this message .
– Rudda Beltrao
Have you adjusted the version of your APK? The versioning is for this, like 1.0.1, 1.0.2, etc. In Gradle if it is something like
versionName "1.1"
change toversionName "1.2"
or greater, it must be this.– Guilherme Nascimento
I changed the version and at the terminal Ionic Cordova build android --Prod apparently it was not alternating the version without a build.... I appreciate the tip. problem solved
– Rudda Beltrao
increase "versionCode" of your app... will work!!!
– FlipNovid