[TIMOB-2543] When using an Archived Application build from XCode (Generated by Titanium Distribute), code resigning for Ad-hoc distribution from XCode doesn't work
I can sucessfully use Titanium for Ad-hoc distribution using the "Run on Device" option inside the Titanium Developer, but when I go for "Distribute", ad try to Share the application from XCode Organizer it generated the new ipa but it gives me errors with entitlements.
STEPS TO REPRODUCE:
Go to Titanium Developer 1.2.1 ( Titanium Mobile 1.4.2 ) and
select Test & Package.
Select the DISTRIBUTE tab.
Use your app store Provisioning Profile and Standard Distribution Profile. ( iOS SDK 4.2 )
It generates an Archived Application on XCode
Go to XCode (3.2.5), under the Organizer, select your application under the Archived Applications.
Click on your packaged build.
Send to Apple / Appstore ( NOT SURE IF THIS STEP IS REQUIRED, BUT I DID IT )
After app submission, click on "Share..." button.
Select one Ad-hoc Distribution (iPhone Developer: xxxxxxxx) for your app ( that already works flawlessly with Titanium "Run on Device" )
Now do either of those steps ( all of them fails ):
TRY TO LOCAL DEPLOY:
Click on Save to Disk and the move the generated resigned .ipa to iTunes, it gives an entitlements error ( probably a error with code signing )
TRY TO DO WIRELESS ENTERPRISE DISTRIBUTION ( Works with no problems with Titanium - Run On Device option, but not with XCode code resigning ):
Click on "Distribute for Enterprise..." enter URL (your full URL
to the generated ipa file), Title, Subtile and Image options for
Upload everything to your web-server (.plist and .ipa files to the same path).
Create an HTML file with a link to href = "itms-services://?action=download-manifest&url=http://YOUR_URL_PATH/YOURAPP.plist")
Open the URL on your iDevice and click the link to install.
The process will start but will fail (Download problem). ( it doesn't fail with Titanium generated Ad-hoc ipa )
- Stephen Tramer 2012-07-26 Mentions Titanium Developer. No longer available. We also provide adhoc builds which should handle this.