What I ended up doing was figuring out that you need to specify an Ad-Hoc provisioning profile. Sadly, we have too many.
Currently looking at better solutions. Will advise the list when I find them. Have a weekend. All the best, Alex Zavatone On May 22, 2015, at 11:34 AM, Zack Morris wrote: >> On May 20, 2015, at 9:13 AM, Alex Zavatone <[email protected]> wrote: >> >> My god, I figured it out. No idea how though. >> >> This process is simply hideous. >> >> The error messages in the edge cases point everywhere except the correct >> solution. >> >> Basically, I was trying to codesign and distribute an ad-hoc app. >> >> It's amazingly obtuse and even harder than it was 2 years ago due to the >> potential paths for failure. >> >> So nice to see that things are improving for us iOS developers form the >> tools side. >> >> >> But we have new animations everywhere as compensation, so we have that. >> >> >> Ugh. > > I here ya. One thing that worked for me was trying to use the > managed-by-xcode certificates because they seem to update themselves better > now, especially for teams. That way you can just choose “Automatic” for > provisioning profile and “iOS Developer” or “iOS Distribution” for code > signing identity in the project settings or target settings. > > Also if you go to Xcode->Preferences…->Accounts->View Details and click the > reload icon in the lower left, it seems to fix strange problems that the > normal fix certificate issue dialog doesn’t. > > I honestly don’t remember whether Ad-Hoc requires development or distribution > certificates, or other trivia like that. I just keep it all in a big notes > file and fall back to trying every combination if in doubt. > > It all reminds me of the time back in the 90s when you used to have to type > in a bunch of TCP parameters to connect to your ISP, or fill out a bunch of > POP/IMAP info to connect to an email account, when username and password > should have sufficed. For provisioning, the only thing that should be needed > is a private key (everything else is friction) so I’m hopeful that Apple will > come around and axe most of the manual data entry that’s required now. It’s > not just Apple’s problem though, because right now the way that keys are > managed for things like SSL and SASS APIs and push notifications, or anything > that requires server communication is such a convoluted mess that I simply > don’t think it’s the way it will be done in the future. Probably what’s > going to happen is we’ll get something like OpenID for private communication > and you’ll just keep all of your keys in a private wallet like Bitcoin and > any protocol that requires more than that single key will be considered > antiquated and fall out of fashion. > > Zack Morris > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Xcode-users mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/xcode-users/zav%40mac.com > > This email sent to [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
