This question is locked. New answers and comments are not allowed.
I've ported an App developed in another platform for Android. Their automated build system signs the app in a similar way Icenium does. The plan is to replace the current-published .apk with the current version developed with Icenium. However when trying to upload the .apk, the developer console says previous .apks have signature fingerprint [SHA1: 0B.....XY] and uploaded .apk have signature fingerprint [SHA1: B0...XX] and they should be the same. Also, where it's supposed I should specify the package name in order to be the same? Tried in "Application Identifier" inside properties but it reverts back to the initially provided name.
So question is how to replace such certificate or signature so they are the same and the current published .apk can be replaced by the Icenium one ? The Icenium build will be uploaded to my developer dashboard as a Beta build mainly for in-app purchases testing purposes. Once it passes testing, it will be pushed to production.
I'm new to all this of signatures and certificates, so your help will be greatly appreciated.
Thanks.
So question is how to replace such certificate or signature so they are the same and the current published .apk can be replaced by the Icenium one ? The Icenium build will be uploaded to my developer dashboard as a Beta build mainly for in-app purchases testing purposes. Once it passes testing, it will be pushed to production.
I'm new to all this of signatures and certificates, so your help will be greatly appreciated.
Thanks.
1 Answer, 1 is accepted
0
Hi Alfredo,
The error you've received from Google Play does not seem to be related to App ID, it only mentions that the certificate is not the same and therefore you would not be able to update the existing app. Note that in Icenium you have Run and Publish menus, the Run menu has options to build and run your app in Icenium Simulator or for developer/ad-hoc testing. The Publish menu however is for building your app in Release mode, so that it could be published to Google Play Store. Make sure that the app you're trying to upload is not build via the Run menu, it should be build via Publish.
If the above is correct, then double check the certificates you use to sign the app, it should be the same used to initially sign the app.
Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
The error you've received from Google Play does not seem to be related to App ID, it only mentions that the certificate is not the same and therefore you would not be able to update the existing app. Note that in Icenium you have Run and Publish menus, the Run menu has options to build and run your app in Icenium Simulator or for developer/ad-hoc testing. The Publish menu however is for building your app in Release mode, so that it could be published to Google Play Store. Make sure that the app you're trying to upload is not build via the Run menu, it should be build via Publish.
If the above is correct, then double check the certificates you use to sign the app, it should be the same used to initially sign the app.
Regards,
Steve
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.