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.
Related
I'm getting this error when uploading my app to the Google Play Store. What am I doing wrong?
You uploaded an APK or Android App Bundle signed with a certificate that is not yet valid. You need to sign your APK or Android App Bundle with a certificate that is currently valid. Find out more about signing. You need to use a different package name because "com.example" is restricted.
Google play will not allow you to upload packages with the name com.example. Rename your packages from com.example.* to com.sonib.* (for example)
Click the link in the error message to learn how to sign your app with a valid certificate. Follow the steps to get a certificate and sign your app. Note: You may need to purchase a secure certificate. This is required to upload public applications to the Google Play Store.
How to sign your app: https://developer.android.com/studio/publish/app-signing
Here is one example of where to buy a certificate: there are many possible vendors, so feel free to shop around.
Where to buy a certificate: https://www.websecurity.symantec.com/code-signing/android
The error message you provided says com.example is restricted as APK package name, so the issue is clearly that you named your application this, which is invalid on Google Play.
Change your project name and you should be good to go.
I have not run into this issue on the Google Play Marketplace, but I would imagine you will also get the same error of you attempt to use the same package name as an application already published in the store.
As far as the certificate goes, I am assuming you are using Android Studio. Simply build a Signed APK from the build menu. This is how I create the APKs I publish on Google Play and I have never had an issue.
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'm trying to upload and app to Play Store. I built the app in HTML5 and It was compiled with Cordova, using Intel XDK. When I try to upload the app to Google, I got a message like: "The certificate (digital sign) of past application are different of new".
The older app is an Android WebView, compiled using the IDE: Eclipse.
How can I sign an android app with the same value of older application?
You need to sign the app using the same certificate you used the first time you uploaded to Google.
Typically, when you generate the signed APK, you have to select a keystore path (or generate a new one), in your case you need to select the same one you used before. i.e. <your_app>.jks
If you no longer have this keystore then you cannot upload a new .apk, your only solution would be to unpublish your currently uploaded app and create a new one with your new signed .apk
If you do have your old keystore, but cannot remember the information within it, you can Google the commands to retrieve data from the keystore, (based on your OS).
I have uploaded on apk file on the google play account,
apk i have created from eclipse by right click on the project and export and put following details in it
password,alias and developer units only.
and i have uploaded successfully on google play account.
But now problem is i have deleted this apk from local and also i am unable to uplaod any other apk if try to update 2nd apk with version code = 2 and version name = 1.0 then also it is giving me error that
The apk must be signed with the same certificates as the previous version.
So please help me to solve this issue now what can i do to upload a new updated apk in this application.
You are not using the same keystore file to sign your apks.
the .apk 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 and will not offer it to users as an update.
Taken from here,
The apk must be signed with the same certificates as the previous version
The only way is to sign your update package apk with the same key which you have used for the previous version. No other go. Google is strict about it.
For the same application you are updating it's version. Then there is
no need of having previous apk file but there should be same keystore
which you have used to sign the first apk file which is on google
play. Also follow the same steps which you have done for first apk
file.
In case you don't have same keystore then :( you simply cannot update the same application as of now.