I have uploaded an app on Google play store. After uploading i made minor changes in the app. Is there a way to apply those changes to the play store?
Do i have to upload a new apk or create a new version of the app ?
Update your apps
Prepare your APK
When you're ready to make changes to your APK, make sure to update your app’s Version Code as well so that existing users will receive your update.
Use the following checklist to make sure your new APK is ready to update your existing users:
The Package Name of the updated APK needs to be the same as the
current version.
The Version Code needs to be greater than that current version. Learn
more about versioning your applications.
The updated APK needs to be signed with the same signature as the
current version.
To verify that your APK is using the same certification as the previous version, you can run the following command on both APKs and compare the results:
$ jarsigner -verify -verbose -certs my_application.apk
If the results are identical, you’re using the same key and are ready to continue. If the results are different, you will need to re-sign the APK with the correct key.
Learn more about signing your applications :-
Upload your APK
Once your APK is ready, here’s how you can upload the new version using your Developer Console.
Sign in to your Google Play Developer Console.
Select your app.
On the left menu, click APK .
Click the Upload new APK button.
Upload your APK.
Select a publishing option.
Delivery of updates
After you've submitted an update to an app, you’ll see “Update pending” near the top right of your app’s Developer Console pages while your app is being processed. Once the update is published, your update will start being distributed to existing users and the “Update pending” status won’t be displayed.
Once your update is available, users can download the update on your app’s Store Listing page or from their
My apps page on the Play Store app.
Also, if a user has turned on automatic updates for your app, the update will be downloaded and installed automatically.
App updates take some time to be delivered to existing users. If you've submitted an update that hasn't showed up on Google Play, please wait at least 24 hours before contacting our support team.
https://support.google.com/googleplay/android-developer/answer/113476?hl=en
You have to increase the version code and have to create new signed apk.
Steps:
Make your project ready for publish (remove logs, remove unused import statement and resources etc.)
Increase version code in manifest file. You can increase version name but its not mandatory, its depend upon the changes you are doing in the application.
Generate signed APK with your .keystore or .jks file.
Upload APK on Play Store.
Go through this link for more information.
Yes , You can update an existing app w/o changing its version name. The version name is what the user will see on Google Play (i.e. version 1.10, 2.08, etc.), and has nothing to do with the actual version number of your application (it can be anything you want).
According to this article you have to increment your app version and upload the new APK. I recommend reading this article to get an overview of all instructions to update your app.
Yes, you can do changes. After finished changes, you just need to increase version code and generate new signed bundle for your app.
Create new release in google play console and roll out it.It will be mirrored with in few hours in playstore.
Related
In the recent try for uploading a new version of apk for existing application to PlayStore, threw an warning message as mentioned below
So the question is, is it mandatory to upload only aab files to PlayStore or normal apk file can also be updated.
If aab file has to be uploaded, then how to sign the aab file before uploading.
I referred this Link for Goolge App signing. Is this also required ?
Note:
The application developed is a cordova application. So if the above mentioned things are mandatory is the procedure different to build for cordova application ?
Thanks in advance !
"Important: In the second half of 2021, new apps will be required to
publish with the Android App Bundle on Google Play. New apps larger
than 150 MB must use either Play Feature Delivery or Play Asset
Delivery".
Taken from
https://developer.android.com/guide/app-bundle
So the question is, is it mandatory to upload only aab files to PlayStore or normal apk file can also be updated
Normal APK can also be uploaded / updated. This is just a warning and not an error message. Google Play will still allow you to continue
If aab file has to be uploaded, then how to sign the aab file before
uploading.
In Android Studio, when building signed APK / AAB, it will ask you to export an encrypted key. Take note of the location because you will use this exported key when you upload your AAB. See highlighted in yellow
I referred this Link for Goolge App signing. Is this also required ?
Nope, it's optional. Quoting Google Play Support:
Using app signing by Google Play is optional. You can still upload an APK and manage your own keys instead of using an app bundle. However, if you lose your keystore or it becomes compromised, you won’t be able to update your app without publishing a new app with a new package name. https://support.google.com/googleplay/android-developer/answer/7384423
we are developing a mobile application for one of our clients, and the client currently has an app version on Google's Play Store.
The current app has been developed by an external vendor A, so our client has been uploading the apps with his signature.
Now, we want to go on production with the new app developed by us (We are the vendor B).
The client has given us the keystore file used for signing, the key alias and the password, so we are able to generate an APK with the same package name (com.myclient.myapp). We are signing with V1 (The same way the old app has been signed).
The problem starts when we try to update from the old app to the new one. In an Android device, we install old app, and then we try to update to the new one. Android does not allow us to install the new signed APK because understands that the signatures of both apps seems to be different.
We need help on this topic. Can you please help? Thanks a lot in advance!
The package name's should not be matched with the earlier vendor with your changes.
Check the gradle versions before generate the signed APK and upload to playstore.
Check in the manifest the version name and version code are updating.
While generating the signed APK check the check boxes of all with signed full APK.
"App signing by Google Play" is a two step process. You sign the APK with an upload key and then Google checks this signature and resigns the APK with another key.
If this was used for the old App you will not be able to upgrade an App downloaded from the store with one that was locally signed because the signature key is different.
It will however work if you upload the new App to the Play Store.
I'm trying to install new apk for application that I uploaded on play store .. but I got this message (the Package conflicits with an existing package by the same name )
and not able to install application berfor uninstall the past app..
what should I do ?
I won't to force Uninstall on users ..
This is what I'm guessing:
When you upload an apk to Google Play you have to sign it with a proper keystore, resulting in a package-certificate pair. That apk goes with a particular version & version code number, let's suppose 1.0 / 1
If you upload then a version 1.1 to Google Play, you also have to increment the version code. Doing this, downloading the new apk is just an updating, and there is no problem at all. For the system, the app is the same because the certificate and the package are the same.
That is the normal behavior your users will experience.
Now, I'm guessing you are launching your debug apk in your device while developing, which by default uses the machine debug certificate. If you have that debug apk installed when trying to download the deployed version from Google Play, the system needs you to uninstall the previous one, as they are not the same app (different certificate) and the conflict exists.
That's only a guessing, but give it a try.
Regards.
I developed an android app in 2016. Then some gradle files has been deleted accidentally.
Now i want to update and upload my application on Google play. But old source code was not accepting phone to connect while debugging and even not building.
I already have release signature key
package name.
All source code without gradle part.
Can I create another fresh app in android studio with same package name and source code.
New created debug application will work on every phone I know but when I signed it with my previous release key and upload it in Google play will it be accepted or not?
As long as the package name and signing certificate are the same you can build an update for your APK however you want.
For Android apps on Google playstore, package name is considered as your app's identity. Application will be considered as new application only if you change the package name.
Changing only the Keystore will also obstruct the ability to update app on play store and only way to recover would be to create app with new package name.
In your case if you maintain same package name and use same Keystore, there shouldn't be an issue to upload a new release. Since upload on Google Play store doesn't care about the environment used to build the apk.
I get this problem when uploading a new version of my android application :
The APK must be signed with the same certificates as those of the previous version.
I have already make updates using the same private key withoutany problem; but when i update my Android SDK i get this problem.
Please any body know a solution ?
Maybe updating your SDK has changed the certificates of your application, you have to change it in your app.
Publishing Updates on Android Market
At any time after publishing an application on Android Market, you can
upload and publish an update to the same application package. When you
publish an update to an application, users who have already installed
the application may receive a notification that an update is available
for the application. They can then choose to update the application to
the latest version.
Before uploading the updated application, be sure that you have
incremented the android:versionCode and android:versionName attributes
in the element of the manifest file. Also, the package name
must be the same as the existing version and the .apk file must be
signed with the same private key. If the package name and signing
certificate do not match those of the existing version, Market will
consider it a new application, publish it as such, and will not offer
it to existing users as an update.
If you plan to publish your application on Android Market, you must
make sure that it meets the requirements listed below, which are
enforced by the Market server when you upload the application.
Source : http://developer.android.com/guide/publishing/publishing.html#marketupgrade
Check that the updated APK is actually signed with the same certificate as the current version in the market place. To do that I would suggest executing the following command on both APKs:
jarsigner -verify -verbose -certs /path/to/apk
If they are the same then perhaps it is a bug with the Android Marketplace console?
The fact of updating your sdk shouldn't have any effect to your apk uploading.
Check and be sure that you signed your application with the same private key that you generated the first time you uploaded your application in the market, and you incremented versionCode and versionName in your manifest file.