i read it, but his problem was a blank option in xcode. In my case the “command line tools” option is already set to “xcode 4.5.2”.
I try to un/re-install everything again now… [import]uid: 102950 topic_id: 33878 reply_id: 134994[/import]
Hi, I’ve got my app working now on a few Android devices in debug mode with the zoomStretch fix NinjaPig mentioned in his thread. I have 2 questions:
-
when I download the app on the various Android devices the icon shown is the Corona one. Is this always the case when building in debug mode with Corona’s provided debug settings?
-
when I use the keytool command to generate my own key, what name should I use for the ‘mykeystore.keystore’ param’s ‘mykeystore’ field? Is the the actual app name (without spaces, etc.) or is it the package name filled in the Corona build dialog (i.e. com.mydomain.apps.testapp)?
I hope someone here knows the answers! 
Thx! [import]uid: 72317 topic_id: 33878 reply_id: 135006[/import]
Hey, @ken4, I think you need to add your own icons for Android builds. If you don’t, you get Corona’s default icon.
If you search around the Forum (or Android dev sites), you should be able to get the list of icons that should be included with proper dimensions. (Also, it might be a better idea to start a new thread asking about this specific question under Android sub forum – because it’s a bit irrelevant to this thread.) Anyhow, here’s a quick list from mine:
Icon-hdpi.png
Icon-ldpi.png
Icon-mdpi.png
Icon-xhdpi.png
Icon.png
About the keystore name, mine is named beetlebounce.keystore
Naomi
[import]uid: 67217 topic_id: 33878 reply_id: 135020[/import]
ok, it is working now…
reinstalling everything did not help.
there was an old (expired) certificate in my “system” keychain. But it is normaly invisible until one click “view->show expired certificates” in the keychain access menu at the top.
funny thing is that this was there all along and i was still able to build for developer devices until now. And although all current certificates were valid and installed correctly! Something must have changed/updated since my last build… but i dunno what
if you face the same problem try this “solution”
[import]uid: 102950 topic_id: 33878 reply_id: 135052[/import]
Hey, @GbCStudios, glad to hear you got it sorted. There are just too many different ways the code-signing fails, it seems. What a nightmare. I’ll keep your solution in mind too. Thanks for sharing your solution.
Naomi [import]uid: 67217 topic_id: 33878 reply_id: 135060[/import]