IOS Provisioning Portal

Getting Started Newbie Questions
#21

Thats the message I got…

failed to extract requirements data: 1
/Users/siewlantan/Desktop/Fishies.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 880

  • (null)

warning: Unable to extract codesigning entitlements from your application. Please make sure Fishies is a valid Mach executable that’s properly codesigned. (-19050)
/Users/siewlantan/Desktop/Fishies.app/Fishies: invalid signature (code or signature have been modified)

  • (null)

And I cannot install to my device. [import]uid: 203442 topic_id: 34374 reply_id: 136881[/import]

#22

I had the same problem too, a few weeks back…

After messing around, downloading certs, stopping and restarting corona, I basically did what richard9 did, except I used xcode instead of the config util. [import]uid: 9070 topic_id: 34374 reply_id: 136892[/import]

#23

This may be why to are experiencing issues when trying to put your app on a local device. To create an ad hoc provisioning profile:

  1. Log in to the iOS Provisioning Portal from the Member Center.

  2. Select Provisioning in the sidebar.

  3. Select the Distribution tab.

  4. Select New Profile.

  5. Select Ad Hoc as the distribution method.

  6. Enter a profile name.

  7. Confirm that your distribution certificate is displayed.

  8. Select Xcode: iOS Wildcard AppID as the app ID.

  9. Select the devices you want to be able to run the app.

  10. Click Submit.

When the status of the ad hoc provisioning profile changes from Pending to Active, you can begin using it. You may need to refresh the webpage in iOS Provisioning Portal to see the status change. For more information on setting your device for testing, please review the following website:

http://developer.apple.com/library/ios/#documentation/ToolsLanguages/Conceptual/YourFirstAppStoreSubmission/TestYourApponManyDevicesandiOSVersions/TestYourApponManyDevicesandiOSVersions.html
[import]uid: 180288 topic_id: 34374 reply_id: 136908[/import]

#24

I had to renew my apple developer account and issue new certificates a couple of weeks ago and I’ve been running into the same problem.

The certificate process had changes slightly since my first time around with it a year ago but it “felt” like I did everything correctly.

Posting up on this thread in case anyone has any input on this problem.

Thanks [import]uid: 105707 topic_id: 34374 reply_id: 136638[/import]

#25

The basic process:

  1. Create your Certificate.
  2. Add your test devices to the provisioning portal.
  3. Create an AppID
  4. Create a provisioning profile that combines your cert, your devices and app ID. There are three profiles you need: developer, distribution Ad Hoc and distribution Store. The first two require your devices to be added, the store version doesn’t need devices. Personally, I rarely use the developer profile (only needed for some testing).
  5. Download the profile and install it. I prefer to copy/move the profile from my Download’s folder to my /Users/myusername/Library/MobileDevice/Provisioning Profiles folder.
  6. Restart Corona SDK.

If your device ID is not in the profile, you won’t be able to load the app on your device.
[import]uid: 199310 topic_id: 34374 reply_id: 136680[/import]

#26

I did everything corona tutorial steps, I still have this errors :

corona emulator :
Your application built but failed to pass Apple’s validation tests.
No code signature found.
warning: iPhone/iPod Touch: Icon.png: icon dimensions (512 x 512) don’t meet the size requirements. The icon file must be 57x57 pixels, in .png format (-19014)
failed to extract requirements data: 1
/Users/r/Desktop/JC.app: invalid signature (code or signature have been modified)
failed to extract entitlements: 1
AssertMacros: entitlements_requested, At least need an application-identifier entitlements file: codesign_wrapper.c, line: 879

  • (null)
    warning: Unable to extract codesigning entitlements from your application. Please make sure JuegoCosa is a valid Mach executable that’s properly codesigned. (-19050)
    /Users/r/Desktop/JC.app/JC: invalid signature (code or signature have been modified)
  • (null)

Itunes :
iTunes Sync failed to install [import]uid: 180288 topic_id: 34374 reply_id: 136687[/import]

#27

When I attempt to move my built application onto my development devices listed in my Xcode organizer window I get the message:

“The application does not have a valid signature”
I’ve checked my Corona Build for iOS output window and it lists the same type of output warnings that rdchicago posted above.

This was never a problem with any profiles I used off the first year of my apple developer subscription. This has only been a problem the last month now that I’ve renewed and been forced to attempt to make new ones… [import]uid: 105707 topic_id: 34374 reply_id: 136694[/import]

#28

I had some issues on getting my new certificates. Not sure if they are the same, but here’s what I had to do:

First, cleanup:

  1. Load up Keychain and destroy the outdated certs
  2. Remove the expired provisioning profiles from the portal
  3. Remove the provisioning profiles from the loader (I use iPhone Configuration Utility)
  4. Not sure if necessary but I removed the old profiles/apps from my device.

Next, rebuild:

  1. Make the new cert
  2. Download and re-add the cert to Keychain
  3. On the portal remake the provisioning profiles using the new cert
  4. Download the new profiles and install them
  5. Rebuild apps as necessary

This isn’t exact but basically I had quite a bit of trouble getting Corona to look only at the new stuff so the fastest way to recover was to make sure I expunged the old stuff from OSX. [import]uid: 41884 topic_id: 34374 reply_id: 136700[/import]

#29

Hi Rob Miracle , thanks for you post,
I still with the same problem,
Im using a Mac and I can’t find the MobileDevice folder !!! do I need :
/Users/myusername/Library/MobileDevice/Provisioning Profiles folder
?
also I reset my keychain access and now my certificates in corona emulator doesn’t show up :frowning:

thanks [import]uid: 180288 topic_id: 34374 reply_id: 136732[/import]

#30

Mine is here:

/Users/rmiracle/Library/MobileDevice/Provisioning Profiles

I don’t remember having created the folder. I think Xcode made the folder, but I can’t be for sure, it’s been a while.

[import]uid: 199310 topic_id: 34374 reply_id: 136739[/import]

#31

@rdchicago - which folder can’t you find? I recently upgraded from Snow Leopard to Mountain Lion and had to follow these instructions to make my Library folder visible again:
http://osxdaily.com/2011/07/04/show-library-directory-in-mac-os-x-lion/
[import]uid: 105707 topic_id: 34374 reply_id: 136747[/import]

#32

Thanks a lot , i found the mobileDevice folder and I had all certificate I have been using into provisioning folder, but I still having problem with corona SDK when Im trying to build my app for testing in my device, In build option in Code Signing Identity I CANT choose any certificate "
[import]uid: 180288 topic_id: 34374 reply_id: 136772[/import]

#33

Im trying to build my app for testing in my device, In build option in Code Signing Identity I CANT choose any certificate "
Also in Xcode status said : Valid signing identity not found [import]uid: 180288 topic_id: 34374 reply_id: 136774[/import]

#34

Glad that link was helpful, I was really confused when I could find the Library folder through Finder searches but not by looking in my user folder manually. Weird.

As far as my dilemma with getting my builds onto hardware goes, my first step will be to completely remove all my certificates/provisioning profiles/etc. and start fresh to see if I can get something to work.

If that doesn’t work I’ll attempt to build a simple “hello world” app in Xcode to see if I could put that onto a device. It seems like that won’t be successful based on your experience. [import]uid: 105707 topic_id: 34374 reply_id: 136778[/import]

#35

If Corona is not letting you choose any provisioning profile then you likely have a certificate/key problem. I don’t know why Apple had to make this the most miserable thing (outside of push notifications) but its frustrating and you just have to be diligent and go through the guides again. Use Google and search for previous forum posts on this topic. There are tons of suggestions. Here are a couple of threads to get you started:

http://developer.coronalabs.com/forum/2012/09/12/build-errors-probably-certificate-issue

and this seems to have helped a lot of people:

http://developer.coronalabs.com/forum/2011/03/13/build-app-store

[import]uid: 199310 topic_id: 34374 reply_id: 136785[/import]

#36

Rob, thank you for sharing those links and for the perspective that I’m not insane for finding this more than a bit frustrating (the Apple end of things).

The first link sounds very much like my circumstances. The thread implies that I need to have iOS 6 running on my devices, is that correct? I’m still on 5 on my iPhone 4S. If anyone can confirm that that’s the case I will sort that out immediately. Will likely sort it out anyways but I’m trying to be very organized about each step I take.

Thanks :slight_smile: [import]uid: 105707 topic_id: 34374 reply_id: 136827[/import]

#37

Hi there , thanks for u help early today about certificates, finally i fixed the problem ,
since i have my app game installed in my device, do u know how can i block levels in my game or applee store will do for me, for people want to buy other levels in my app ?
thanks [import]uid: 180288 topic_id: 34374 reply_id: 136836[/import]

#38

Well our apps should still run on 4.3, but Apple is likely to pull that plug soon, but 5.x should be fine. If you’re talking about this comment:

@mike470, build 919 only builds for iOS 6.0 and that requires Xcode 4.5. That’s Apple’s requirement, not ours. You could use build 918 but can only build for 5.1.

This is talking about your Mac, not your device. Corona used to link to the 5.x SDK, but as of build 919, we now link to the 6.0 SDK (and give you an option to build against the latest 6.1 beta SDK). Even though we are building against a newer SDK, devices with older OS’s should still be able to run the apps since 4.3 and later is still in the code (for a lack of a better description).

If you want to build for iOS 6.0 as well as older versions, you will need to be running XCode 4.5 with the iOS 6.0 SDK installed on your Mac. Now if you have a newer Corona but an older XCode there might be issues.

[import]uid: 199310 topic_id: 34374 reply_id: 136837[/import]

#39

@rdchicago please create a new message thread for this (I recommend the newbie forum) and ask your question there, so this thread doesn’t get distracted from key/certificate type problems.

Thanks
Rob
[import]uid: 199310 topic_id: 34374 reply_id: 136838[/import]

#40

OK, great news, I’ve got my game running on a development profile on my iPhone 4S that’s running version 5.1.1 iOS…

Very relieved!

The process that seemed to find me success was to delete any profiles or certificates I had on my machine (.cer or .mobileprovision files) and make sure they were deleted from my keychain access. I also deleted all the keys I had in my keychain access so that may have been a factor. I then started fresh with the process of making certificates (one development, one distribution… this may have been a problem previously as I may have made a new dev but not distribution when I first tried a few weeks ago?). After the certificates I used my existing developer Devices and an existing “wildcard” (*) App ID to build a new development provisioning profile. This one works.

It all seems very clear in hindsight but this has taken me a few days of tinkering, research and posting to solve. I have yet to make an Ad Hoc or Distribution profile so I hope that doesn’t kill me again! I feel much more empowered to tackle that now and worse case I’ll just do it all again when the time comes.

Thanks Rob for your input, it really made the difference in sorting this out.

Happy New Year to everyone :slight_smile: [import]uid: 105707 topic_id: 34374 reply_id: 136842[/import]