Validation problem with new Corona public build - invalid signature/codesign wrapper problems

Getting Started Newbie Questions
#21

I think I got past this. For some reason there are 3 seemingly identical provisioning entries in the pop-up list in the iOS build dialog. I get the above error when using the first entry but not when using the second or third.

Even though these all have the same name, do these entries correspond to the ad-hoc, development and distribution provisioning licenses mentioned elsewhere in the docs? If so it would be nice to identify them as such. [import]uid: 72317 topic_id: 33878 reply_id: 134682[/import]

#22

My issue seems to be different from Ken4’s. I don’t see multiple provisioning entries in the iOS build dialog. [import]uid: 135391 topic_id: 33878 reply_id: 134688[/import]

#23

I have the same error “nate2” described.
I have xcode 4.5.2 installed, renewed all certificates and provisioning profiles and they are all valid.
I checked for duplicated certificates as described above. nothing there!

Yet i am still getting the error when i’m trying to build for developer devices.
Building for distribution works fine!

help! i am running out of ideas :-/ [import]uid: 102950 topic_id: 33878 reply_id: 134968[/import]

#24

Hey, @GbCStudios, you are probably facing the very same issue that kurtbieg had to deal with under this thread:

http://developer.coronalabs.com/forum/2012/11/30/error-message-popup-when-first-time-use-xcode-452-build-971#comment-134700

Good news is, kurtbieg eventually solved the problem. You should hop over there and read through the thread, and see if you can solve yours too.

Good luck.

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134969[/import]

#25

@ken4, launch Xcode and check the provisioning profiles listed under Windows > Organizer. It’s the very first in the Organizer window under LIBRARY section. You’ll see all the provisioning profiles, and you should just delete/remove the ones that are no longer valid. And then, relaunch Corona Simulator. Once removed from Xcode, the invalid provisioning profiles should not appear in the drop-down when generating a build. If you don’t see any provisioning profiles, click on Refresh at the lower right corner, which will import all of your provisioning profiles for you, and then you can isolate and remove the ones you don’t want.

Edit: By the way, you can rename the provisioning profiles at Apple Dev center. Once you rename it to more recognizable names, you shouldn’t have any trouble selecting the one you want to use.

@nate2, I’m not very sure why it’s happening to you, but just in case… are you using the latest version of Xcode? I don’t remember exactly when the Xcode upgrade requirement took place in relative to Corona builds, but I remember at some point this year, the Xcode update was necessary to build for more recent version(s) of iOS. I believe it was Apple’s mandate. My Xcode version is 4.5 and I have no issue generating device builds.

Edit: @nate2, I’m now wondering if you are having the very same problem kurtbieg is having. Please see his post here (and ensuing posts). Sounds like a nightmare (just like the one I had with renewing my certificate yesterday):
http://developer.coronalabs.com/forum/2012/11/30/error-message-popup-when-first-time-use-xcode-452-build-971#comment-134700

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134690[/import]

#26

Thanks, Naomi. Yes, it looks like the same problem as kurtbeig’s. I apparently fixed it, though. I was already running XCode 4.5, but I just updated to 4.5.2 and I’m not getting the error anymore. Very strange. [import]uid: 135391 topic_id: 33878 reply_id: 134720[/import]

#27

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]

#28

Hey, nate2, glad to hear you got it fixed!!

Naomi

P.S. BTW, yeah, this whole thing about code-signing is nightmarish. My certificate expired a couple of days ago, and getting it renewed required me to completely clean slate my keychain. Yikes. But at least I didn’t have to reinstall OSX, which, apparently, some other user had to do to get it to work. [import]uid: 67217 topic_id: 33878 reply_id: 134724[/import]

#29

Hi Naomi,

Thanks for the response and the insights. I’ll revisit this shortly and see if I can get it all working as you suggest with distinct names, etc.

Cheers!

Ken [import]uid: 72317 topic_id: 33878 reply_id: 134726[/import]

#30

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! :slight_smile:

Thx! [import]uid: 72317 topic_id: 33878 reply_id: 135006[/import]

#31

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]

#32

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]

#33

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]

#34

I think I got it all working with the provisioning files, etc. on multiple devices. Tomorrow, onto trying to actually submit the app to the App Store. Hopefully the screenshots I’ve taken are acceptable resolution/size-wise…

Cheers! Ken [import]uid: 72317 topic_id: 33878 reply_id: 134785[/import]

#35

@Ken, glad to hear it. Good luck with the app submission & approval process!

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134844[/import]

#36

Hi Naomi,

I think I just successfully submitted my app! Now to see what happens with the review process.

Just to verify, once I setup the app in iTunes Connect and then upload the app using the Application Loader tool, the status of my app is “Upload Received”. Is that correct and I now simply wait for an approval email or is there anything else to do?

Also I didn’t have a dedicated support website so I put in a temp link and will create one shortly. Anything specific I need to put on that page?

Thx!

Ken [import]uid: 72317 topic_id: 33878 reply_id: 134864[/import]

#37

Hey, Ken, I believe “Upload Received” will eventually change to something else. I don’t remember what exactly. But it sounds like you’ve taken the right steps to me.

About the support link, I don’t remember reading any specific requirements for it, but you may want to at least include how your users may contact you. You could also include FAQ (if you think there’s going to be a lot of common questions your users might bring up?) With Beetle Bounce, I gave it the URL for our main contact page.

Here’s the Beetle Bounce’s iTunes screen, and notice “Beetle Bounce Support” link. It launches the URL I supplied:

https://itunes.apple.com/app/id471409331?mt=8

I hope this helps.

Good luck!

Naomi
[import]uid: 67217 topic_id: 33878 reply_id: 134868[/import]

#38

Hi,

Yup, I received an email and it changed to “Waiting for Review”.

Thanks for the notes on the web support page. I’ll implement that later today!

Cheers, Ken [import]uid: 72317 topic_id: 33878 reply_id: 134887[/import]

#39

I have the same error “nate2” described.
I have xcode 4.5.2 installed, renewed all certificates and provisioning profiles and they are all valid.
I checked for duplicated certificates as described above. nothing there!

Yet i am still getting the error when i’m trying to build for developer devices.
Building for distribution works fine!

help! i am running out of ideas :-/ [import]uid: 102950 topic_id: 33878 reply_id: 134968[/import]

#40

Hey, @GbCStudios, you are probably facing the very same issue that kurtbieg had to deal with under this thread:

http://developer.coronalabs.com/forum/2012/11/30/error-message-popup-when-first-time-use-xcode-452-build-971#comment-134700

Good news is, kurtbieg eventually solved the problem. You should hop over there and read through the thread, and see if you can solve yours too.

Good luck.

Naomi [import]uid: 67217 topic_id: 33878 reply_id: 134969[/import]