- This topic has 18 replies, 7 voices, and was last updated 10 years, 3 months ago by
.
-
Posts
-
Hello, I am trying to update my application on the google play store. But It wont let me go passed uploading the updated apk file. It keeps saying this apk file is debuggable. Is there something that needs updating with the software? As i never used to get this error?
Thanks
Are you providing your own signing identify files when building the app, (e.g., private key/cert or p12)?
If no then then MobiOne app center creates the android app using a temporary developer certificate and configures the app for debug mode.I was using the developers certificate. one via the mobione build center. This wasn’t a problem when uploading apps before to the play store. I had a problem with this via Apple and the app store.
How would I go about obtaining these private key/cert or p12 so that my app can be updated? This must of been a new change to the Google play store.Thanks again.
Also, my original one I uploaded to the google play store didn’t need me to add any certificates. I think these we’re done automatically via the software.
I found something on your site which generates certificates and password file. Although this worked when building it via the mobieone design and build center. The problem I now face, is that When uploading and updating my previous app which was built 2 months ago, i now have the following message!
Upload failedYou uploaded an APK that is signed with a different certificate to your previous APKs. You must use the same certificate. Your existing APKs are signed with the certificate(s) with fingerprint(s):
[ SHA1: 53:40:8E:10:B8:9E:AE:0E:3E:F3:C7:84:79:8E:21:7F:92:9C:D3:6B ]
and the certificate(s) used to sign the APK you uploaded have fingerprint(s):
[ SHA1: 5C:F0:C1:8B:AB:FB:44:4B:A8:03:A5:96:ED:5F:A2:60:1D:82:67:ED ]
I didn’t even use a certificate before, So i can’t even use that? SO trying to use a new one I was unable to add my update.
What can I do about this? I have a pc and I cannot download the app again to try and disect it. This was why I purchased this software..
Thanks for your help.
>my original one I uploaded to the google play store didn’t need me to add any certificates.
That was a big mistake on us to not have always had in place a policy that all android builds targeted to the play store must be buildable without the user taking direct responsibility for managing his signing details. One reason is what you are encountering now; there is no explicitly managed signing certificate by you or mobibone.
I’m not sure this is easily resolvable since we do not maintain temp certificates for an extended period. Let me ping the dev team to see what options there may be.
Update: my discussion with dev team concluded as I suspected.
Google play requires your app update be signed with the same certificate as the old version. In this case your app was signed with a tmp certificate which no longer exists. Thus you will not be able to update the app directly. Instead build your app with a new certificate. Save this certificate in a private and safe recoverable location. I’m not a google play expert but I believe you need to create a new app in google play for your app and upload the binary to it. Then delete or refer your current app to it.@support-michael wrote:
I’m not a google play expert but I believe you need to create a new app in google play for your app and upload the binary to it. Then delete or refer your current app to it.
Could you please explain this a bit more? What do you mean by upload the binary – to where? And how do we ‘refer’ our app to it?
I just created my first real app in MobiOne and it works flawlessly. For my needs, I do not need it uploaded to the Play store. However, one of my next apps will need to be uploaded and like the OPP, I need to know how and where to get this ‘certificate’ and the process involved in successfully uploading it to both the Play store and Apple App store. I watched all the tutorials and they do an excellent job of explaining how to make the .apk and apple file, but no mention of the rest of the process. And I do understand I need to pay $99 to become an Apple Developer (which I feel is reprehensible that you have to pay to create apps that help solidify their product).
Thanks for helping us. I am ALMOST there.
Mike
I believe upload the binary he is referring to uploading it to the Google Play store (or Amazon App Store).
In the original app that you want people to stop using and use this new one you can edit the description and put a link to the new app. While people can still download the old one, hopefully they will see the info and use the new one.For the certificates you can use the Mobione singing utility: http://2point0m1.mobionesigning.appspot.com/signing/
This is the tutorial on building apps:http://www.genuitec.com/mobile/docs/buildandroidapp/buildandroidapp.html#introduction
For google play uploads try this: https://support.google.com/googleplay/android-developer/answer/113469?hl=en
It has or links to all the info you should need.@CincyPlanet wrote:
I believe upload the binary he is referring to uploading it to the Google Play store (or Amazon App Store).
In the original app that you want people to stop using and use this new one you can edit the description and put a link to the new app. While people can still download the old one, hopefully they will see the info and use the new one.For the certificates you can use the Mobione singing utility: http://2point0m1.mobionesigning.appspot.com/signing/
This is the tutorial on building apps:http://www.genuitec.com/mobile/docs/buildandroidapp/buildandroidapp.html#introduction
For google play uploads try this: https://support.google.com/googleplay/android-developer/answer/113469?hl=en
It has or links to all the info you should need.If you are not being compensated by Genuitec then you darn well should be.
Thank you deeply.
Mike
This is a massive concern. As I have one application which has 4,900 downloads and will need updating in the near future. The current one I need updating has only 400 which is still very frustrating as I have built up a client base with them. As I deal with affiliate based applications.
This is extremely worrying. This was why I purchased this software. Is there no way of retrieving the ‘fingerprint’ within the uploading apk file?
My larger app which has 4+k downloads needs to be updated due to me selling the application and enabling me to change the affiliate code within. Which one has just sold recently for $5k, I am extremely concerned that this will jeopardize my approach with any possible buyer.
Is there anything that can be done about this???!This isnt a problem with Mobione software, M1 will use whatever certs you supply it with. Another route you might want to look into is contacting the support services at Google Play to see if they have any recommendations.
It looks like you might be able to extract the x509 from an APK using openssl:
http://stackoverflow.com/questions/13692917/extract-raw-x-509-certificate-from-a-signed-apk-or-jarFor further research try these posts:
http://stackoverflow.com/questions/11361452/getting-certificate-details-from-an-apk
http://stackoverflow.com/questions/4324120/how-to-view-the-identity-of-person-who-signed-the-apk-on-android-deviceCan this be done by PC
I don’t have an android device at present. Im not sure what these open ssl things are to be honest. I remember trying to covert a file in to p.12 once for apple which was hapless. I can see this being a nightmare.Yes, you can download openssl here: https://www.openssl.org/
I would expect if you can do it its not going to be an easy process…I have having a lot of difficulty extracting the necessary digital certificate (cer.)file and my private key file from my apk application. This was the whole point of me buying this software. I wish to update my application but because it was set to a default file and private key i am unable to extract them. I am finding this opensll way extremely difficult.
Can this be done via your support?Thanks
