Copy Android Certificate from app in old builder

[Ole Henrik Oftedal]

Hi !

I have now almost managed to migrate existing app to new HTML5 builder .

I exported my app as a Tiggzi Plugin (whole project). Then I created a new app based on this plugin.

Is there a way I can copy the Android Certificate from my old application? I want to do an upgrade of my existing Google Play App.

Because when I upload new APK to this existing App I get this message in Google Play:

"
Upload New Apk.
The apk must be signed with the same certificates as the previous version.
"

Ole.

[Maryna Brodina]

Hello! Here is the way to extract certificate from your app.
To use it in another app folllow these steps:

1) create a project backup
2) find "metadata.xml" file in backup archive, open the file
3) find line that contains "autogenerated.crt" - there you can see it's id
4) in backup archive, search for file with according id
5) extract (copy) this file
6) rename the copy to "any_name.crt"

7) open your new app
8) Project - App settings - Android binary
9) uncheck "autogenerate"
10) click the change button for keystore file and load the new one ("any_name.crt")
11) Copy "key alias", "key password", "keystore password" and "package name" from the old app

[Ole Henrik Oftedal]

Hi Marina!

I think I need your help on this one. I tried to follow your recipe

Copy certificate from App: TimeflexApp_old
to App: TimeflexApp

When I try to do this myself I get:

"Oh no! It wasn't supposed to happen but the build failed.
Please try again or view the build errors for more details.
You can also email us support@tiggzi.com and tell us about this problem"

The view link (view the build errors for more details) is a dead link.

I 've shared both projects with support@tiggzi.com.

Ole

[Maryna Brodina]

We'll take a look

[Ole Henrik Oftedal]

Maybe I must rename the old App to the original name first. Then take a backup. Then rename again both apps to _old and to the original and future name for the new app. And then follow your recipe?????

(Did you understand me now?)

[Ole Henrik Oftedal]

Hey wait a sec

Theres two lines with auto "generated.crt". Which one to pick?
I can try the second one now...

[Ole Henrik Oftedal]

YEEEEEEEEEEEEEES!!!!

"We are done! Your APK file was built successfully."

I had to choose the file from the second line containing "autogenerated.crt"
This line had a completely different file name.

This time Google Play accepted the new upgrade.

[michaeldanwild]

Good morning I tried to follow this procedure, but couldnt find autogenerated.crt in the metadata.xm file.
Has something changed?

[Maryna Brodina]

Hello! Now it's not possible. Please share your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a so we can extract certificate and passwords.

[michaeldanwild]

Phew, that's a relief! I was concerned lest it was my fault.
The app is shared with Appery support Name Ashtav ref projects/60288fe2-
Google want me to use these certificates:
[ SHA1: 18:12:1D:7C:FD:8E:2A:6F:63:32:5B:A2:BC:48:0C:5D:4F:0C:68:7B ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 5D:19:94:00:93:D7:7B:C9:36:4B:B9:A3:3B:67:BF:62:A6:AC:E2:F3 ]
One page of this app will be updated several times a year, will it be necessary to go through a similar procedure?
Dan