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.
Related
I recently changed the package name and application id of my android application because when I was uploading the package, google play console thrown an error that example cannot be the package name. So I changed it and now when I install the app in my phone as debug mode then things are working same and properly as expected. Now I created a singed apk and now I have a confusion that do I need a new jks Keystore file or I can proceed with the old one?
Keystore is used to sign android apps. We can sign as many apps we want. So when I changed the application id and package name, this is now a new app. As I said we can sign many apps. We can sign this app also. So no worries we can proceed.
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.
We are developing an Android app and I made an apk available through a web site for our pilot users. The users have Install from unknown sources setting enabled. The app installed and worked fine.
Now I uploaded a newer version of the app. We have changed the version number on the apk package and the new version requires more permissions from the phone, like Prevent phone from sleeping when the first version only needed Full network access.
When I download and open the new version it says "Do you want to install an update to this existing application... Then updated application will get access to:" and then lists the added permissions under a New tab and all permissions under All.
So the installation identifies that this is an update and what has changed in terms of additional permissions.
When I go forward with the installation the installation stops with the message "An existing package by the same name with a conflicting signature is already installed".
What do I have to do/change to be able to upgrade the existing app?
All android apks are signed with a key. Even debug builds. FOr debug builds your IDE will automatically generate a key for you. You cannot update a package that was signed with one key for a package signed by another key. They must use the same key. If you're handing out debug builds not made on the same machine, its likely two keys were used.
The only way to fix this now is to have them uninstall and reinstall. Then make some internal policies about what key to use. To prevent that at my work we all use the same debug key (we have a separate release key so we don't accidently upload a debug build).
The old application had a signing signature A, but the new application got a signing signature B.
Typically, perhaps you create your applications by using the debug keystore. If it is the case, it's not a good thing to do. But as it is a "unknown source", it's not very important.
Secondly, you probably create the new version on another computer than the old, that means a different debug keystore is used.
A keystore is used to check is the producer has not changed between two updates of an application. This is a secure protection.
In your specific case, I suggest you to get the debug keystore that was used for the old version, and use the same when you compile the new version.
The debug keystore is in .android directory in the User directory of your computer (perhaps a hidden folder).
Beware that a specific debug keystore is only usable for 365 days, starting when the keystore is created.
If you want to avoid this problem, please use a release signing key.
https://developer.android.com/studio/publish/app-signing.html
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.
I made an Android App and posted it in Android market, and now I'm made some updates on my Apps and trying to give a next version of the same app. The problem is I missed my KeyStore file I generated previously. But I'm having my old vesion APK file. Now I'm not able to upload the next version, the developer console says
The apk must be signed with the same certificates as the previous version.
as error. May I get any help to make new version for my android app now..?
There's currently no way of retrieving a lost signing key. What you can do is get a new one, pull your app from the market, and upload your update using a different package name.
Sorry, as far as i know you are not allowed to update your application now.
To update existing application on market, you must have that KeyStore file and also remember the password.
Your best bet is to unpublish the old apk and publish a new apk signed using a new keystore.
Please make sure that you have the previously used key store file with you
As per the documentation available on developer.andoird.com you must do the followings
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, Google Play
will consider it a new application, publish it as such, and will not
offer it to existing users as an update.