Android Question App signing

When I first loaded the application into Google Play, I chose «Google signing app...”. The application itself in В4А was signed with a debug key, which Google replaces with its own. While the apk-file is being used, everything is fine - the application is working signed by google-generated key, the license is being checked, etc. But the app bundle cannot be signed with a debug key. I know how to create, store and use an key in B4A. The question is different.

Is it possible to reset the download key (developer key) so that I can replace the current debug key with a new one and Google will accept it?
Or, may be, generate new key with the present debug key data, for signing app bundle by this new?
 

Erel

B4X founder
Staff member
Licensed User
Longtime User
It is a mistake to upload apps signed with the debug key.
But the app bundle cannot be signed with a debug key.
It is possible to workaround this.
Make a copy of the debug key (it it in the Program Files folder). You will need to change the alias with the #SignKeyAlias to androiddebugkey. The password will be android.
Load it as a regular key.

Is it possible to reset the download key (developer key) so that I can replace the current debug key with a new one and Google will accept it?
Or, may be, generate new key with the present debug key data, for signing app bundle by this new?
If I understood correctly, the debug key is the upload key. You should request a new upload key.
 
Upvote 0
Thank you, Erel! With Debugkey, like you explain, it works, and app bundle successfully uploaded to Google Play. Of course it was mistake with debug key, but happens like happens.
Of course, I'll try to request a new upload key.
 
Upvote 0
Top