Currently Being ModeratedMar 22, 2012 8:02 AM (in response to johnlove123)
5) Code Signing Identity appears = "John Love (iOS Distribution)"
Click to expand the list and make sure it's the correct adhoc distribution that's selected.Mac OS X (10.7.3)
Currently Being ModeratedMar 23, 2012 9:13 AM (in response to xnav)
I wonder if "my cousin Vinney" would cop a plea of insanity ?
To continue, here's an update:
1) Provisioning Profiles in the Finder:
2) Xcode Target:
3) Xcode Signing Identity popup:
4) Xcode Organizer:
Now, what's really weird is that if I refresh (via the icon in lower-right corner), the Ad Hoc Distribution and the App Store Release profiles disappear both in the Organizer and in the Finder folder "Provisioning Profiles".
5) Even with this disappearance, in my iOS Provisioning Portal all is intact:
I definitely need some help here - either mental or legal would be gratefully accepted.
Currently Being ModeratedMar 24, 2012 9:52 AM (in response to xnav)
A horrible thought just occured to me.
Namely, I did update to Xcode 4.3.2
And, regular Software Update updated iTunes
BUT, I have the original iPad, not #2 or #3
Is THIS the cause, namely the older iPad.
Currently Being ModeratedMar 24, 2012 10:30 AM (in response to K T)
I have done the following:
1) created brand new Ad Hoc Distribution + Development Provisioning Profiles (all of which the Organizer stares are valid)
2) left the iOS Team Provisioning Profile alone (also, listed as valid in the Organizer)
3) created a new ios_distribution.cer and ios_development.cer which are listed as valid in Keychain Access
4) got away from automatic selection for the Target and Project and carefully chose specific Code Signing Identities
(a) iPhone Developer: John Love (EN96VUN9DJ) Love Song to America development
(b) iPhone Distribution: John Love Love Song to America Ad Hoc Distribution
(c) iPhone Distribution: John Love Love Song to America App Store Release
ALL brand new and listed under both the Certificates and the Devices Detail tab of the iOS Provisioning Portal
5) looking as I write this at the 3 Profiles on my iPad:
(a) Love Song to America development
(b) Love Song to America Ad Hoc Distribution
(c) iOS Team Provisioning Profile: *
ALL listed as Verified √
Currently Being ModeratedMar 29, 2012 3:30 PM (in response to johnlove123)
I would like to add just one basic question ...
Has anyone at all successfully installed an Ad-Hoc app on their real device using Xcode 4.3.1 or 4.3.2 via the current version of iTunes?
Currently Being ModeratedApr 1, 2012 4:38 AM (in response to xnav)
At precisely 0726 hours on April 1st, I just successfully installed my Ad Hoc app on my real iPad.
1) had Entitlements.plist "get task allow" set to YES.
2) should have been NO for a Ad Hoc distribution
3) however, according to my very good friend, TN 2250:
You only need to specify a custom Code Signing Entitlements file if your application is utilizing custom keychain access sharing or iCloud
4) so, I deleted it from the Projects / Targets
P.S. this is no joke, in spite of the date
Currently Being ModeratedApr 1, 2012 8:37 AM (in response to johnlove123)
Here is one way to do it, but it requires that you don't code sign your app.
- Open a new Finder window.
- Navigate to the Xcode.app that you are using.
- Right-click and chose 'Show Package Contents'.
- Click Contents.
- Click Developer.
- Click Platforms.
- Click iPhoneOS.platform.
- Click Developer.
- Click SDKs.
- Click whichever SDK you are using with your iPad.
- Open SDKSettings.plist.
- Expand DefaultProperties and change the value in CODE_SIGNING_REQUIRED to no.
- Change the ENTITLEMENTS_REQUIRED to no.
- Quit Xcode.
- Reopen Xcode.
- Open the project that you are trying to distribute to your iPad.
- Click on the project name, where it has what SDK it is underneath it.
- Click on the Build Settings.
- Navigate down to Code Signing, and expand it if it isn't already.
- Make all of the values in those sub-categories "Don't Code Sign".
You will need root access to do this.
This should solve the problem, because it won't have to check your program memberships, because it isn't code signing.