Problem with signature on Google Play

Question

Problem with signature on Google Play

Navigation

#1 by (1 votes)

3

Some time ago I uploaded an app to Google Play, which Google ended up suspending me.

Now we want to upload the application to Google Play again, but we have several problems.

The first thing is that we do not have the source code of the application, we only have the APK and the keystore. The APK is very well obfuscated which makes Reverse Engineering almost impossible.

The second thing is that, having suspended the Google Play app, we can not remove the old app and upload a new one with the same package name.

We tried to change the name of the package with applications like APK Editor Pro ( link )

And the package name has been changed, but when trying to upload the apk to Google Play we have obtained the following error:

"You uploaded an APK file signed with a restricted certificate. upload a signed APK file with your own certificate. "

We do not know what we can do. Does anyone come up with a possible solution?

Many thanks in advance for reading, the application reached 20,000 users and there are many people waiting for it to come back.

UPDATE:

The mistake I made when signing the APK, in my personal case what I have done is:

Rename the APK package with the PRO APK Editor

Sign the APK with the package changed with APK Signer ( link )

Now Google Play if you accept the APK. Thank you very much to those who have tried to help. Greetings!

android google-play apk

asked by Kike Rodriguez 04.08.2017 в 15:25

source

1 answer

Compatibility between different .net frameworks on the same server Permissions for calls XMLHttpRequest using the Uploadifive plugin

score 1 · Accepted Answer

I answer your questions, I hope to be helpful:

The first thing is that we do not have the source code of the application, we only have the APK and the keystore. The APK is very well obfuscated what that makes Reverse Engineering almost impossible

In this case, ensure that you sign your .apk correctly with the keystore, you can do it manually using apksigner , example:

apksigner sign --ks release.keystore --out production_app.apk debug_app.apk

There are two important things to consider:

If it is an update of the application, the .apk must have the same application package as the current version (package id).
It is strictly necessary to sign with the same keystore or certificate that the current application was signed.

The second thing is that, having suspended the Google Play app, we can not delete the old app and upload a new one with the same name package.

If your application was suspended on Google Play, you will not be able to upload an update , you must upload a new application with a new application package (package id).

Regarding this problem that you comment:

"You uploaded an APK file signed with a restricted certificate. upload a signed APK file with your own certificate. "

you ready two causes:

The .apk you are trying to upload was not signed with a keystore or certificate, check that you are not using a debug one.
A cause that for many is "rare", sometimes arises because the device where you want to perform this task does not have a correct date / time, I mention it because it happened constantly on a PC that controlled their date / time manually.

Now I do not have that problem since the date / time of my pc is synchronized with the network.

There are things I would recommend,

Ensure to have the code backed up and use some code versioning system.
Back up and store in a safe place the keystore or certificate with which you sign your application to Google Playstore.