Maryna,
No it's not identical, as I have been learning I have thought of and implemented improvements. But I did alter the version code and name each time.
I'll delete the versions that I loaded onto Google Play before they made zipalign mandatory.
It's only a six page app so it would be too tiresome to start over.
When we have this resolved will I have to resign each time when a page is modified?
If so do you have any tips?
Thank you
Dan
The issue is that you should upload the same certificate you had used for your first app version. If you deleted app and created new one (with the same functionality) certificate is different. The same if you restored project from backup. So if you don't have original project we won't be able to get certificate unfortunately. Please take a look here https://getsatisfaction.com/apperyio/...
If you're going to delete app and create again it's better to generate your own certificate and keep it stored locally.
Thanks Maryna,
I don't mind deleting and starting again. I have all the material and it's only a six page app.
Dan
Ok, sorry for inconvenience. Just keep in mind it's much more better to generate your own certificates http://developer.android.com/tools/pu...
Good morning Maryna,
I have deleted and rebuilt the app and am ready to publish. I'm not clear on signing. If I autosign and take a copy and then use the passwords for this and future apps would that be sensible?
I'm anxious not to mess up again and I have a larger 30 page app in the pipeline.
Dan
Hello! It's still beter to generate your own certificate, but you can also use autogenerated one. Please share new created app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a which you're going to upload to Google play. We'll extract certificate and send you back.
Thanks Maryna,
I presume the key alias becomes io.appery.project119188.
When I click on keystore file change I get taken to this page. What is required then, or should I leave it as "Name None".
Sorry to ask so many questions, but this needs to be right and your guidance is much appreciated.
Dan
If you're going to use autogenerated certificate you don't need to change anything. If you're going to use your own certificate you must generate it first (outside Appery.io, here is more information http://developer.android.com/tools/pu...). Then click on keystore file change and upload your certificate.
I'm having a similar issue. I've always used the autogenerate, but now it is not working. Also, my backup of the project does not contain files with meaningful names.
Hello,
Could you please specify what do you mean when say [quote:]autogenerate is not working. [/quote]
Do you get any error?