I stupidly posted this on the Ext.js 2.x bugs forums, so I'm manually moving it over to here.
I'm trying to build with adhoc certs so I can send my app around to clients and testers and I keep getting "Invalid IPA: missing embedded provisioning profile. Are you sure this is an ad hoc?".
The profile is adhoc and I can successfully run the build on my device, but inspecting the .app bundle it doesn't look like the embedded.mobileprovisioning profile exists. I'm able to partially work around this problem by copying my mobile provisioning profile used for signing into .app/embedded.mobileprovisioning. So far I've been able to upload to testflightapp and install on my own machine, though I'm not yet sure if my testers have been able to install. If this fails my next attempt will be to use xcrun (see http://nachbaur.com/blog/building-io...c-distribution) to generate the ipa instead of doing it manually:
I've also placed a Default.png in every directory because somebody mentioned on the forums that the fix was to place it in the root, but this has no effect on sencha from what I've seen. I've even tried to drop it into the .app but obviously that invalidates the signature.
Embedding the provisioning profile manually did not work. Testflightapp indeed let me upload the binary, but all of my testers are getting:
"You have not permitted this device to install this build. This device is not included in the build's provisioning profile."
It did let me install the app on my device via TFP, so maybe it's not my adhoc profile that I should copy over verbatim.
I haven't yet produced an adhoc build that runs on more than 1 device, but I did come across some work arounds to remove gloss from the dock icon and adding in a Default.png.
It turns out you can resign the app once it's produced, so after running the sencha packager, simply drop a Default.png into the root of the produced .app, and then edit .app/Info.plist and add (inside the <dict> tags)
Once you've done this you simply need to resign your app like so:
codesign -f -vv -s "iPhone Distribution: You" "YourApp.app"
This will prompt you to resign your app using keychain, allow it.
After this step you can run the following command to verify that your app is usable:
codesign -dvvv YourApp.app
If this command prints out settings you should be all good. You can now produce an ipa that will have no gloss on the home icon and a splash screen. The splash screen only covers up the black screen on startup, and a white screen still appears for a few seconds, but I'm thinking at this point I'm rendering html so I could probably just place an img tag with the splash in my html to cover that bit up too.
I'm also thinking I should be able to drop the embedded.mobileprovision I need into the .app and resign it and I could probably get around the adhoc issue this way. I'm still working on generating that file. I thought it was simply my adhoc provisioning profile exported but apparently it's not.
I'll post an update when I have made more progress.
OK, With the following you should be able to generate an adhoc ipa that is suitable for distribution. Ostensibly this will also work on Testflightapp as well as it let me submit the ipa and then presented me with a list of users/devices to choose from that were in the embedded profile. My testers are all sleeping right now but I'll confirm either way once I know for sure. So far it's looking much more promising though.
For the purpose of this doc, everything is relative to ~/builds.
To start, use sencha package to generate your .app file and move this .app bundle to ~/builds.
1. Open xcode
2. window -> organizer
3. click provisioning profiles in the left pane
4. select your adhoc provisioning profile
5. click export and save this as embedded.mobileprovision in ~/builds
Also, one last quick note.. I was able to get rid of the initial white screen by adding my splash screen as an image in the html and then simply hiding it when my Main view loads. I choose to use the painted listener because onReady and launch fire as soon as my first splash screen ends. Here's the relevant code:
Now (if you also used the workaround in the above post) both the initial black and white startup screens should be replaced with Default.png which will stay on screen until your main components render. Gave my app a much more manageable feel (even though I have 15 second initial startups lol..)