Quote:
Originally Posted by SteveY
[snip]
I've tried cleaning, shutting down Xcode, deleting the build folder, hula dancing. Still nothing. The error message this time is "ambiguous code signing identity".
Nice job Apple.
|
The problem is "hula dancing". It it true that Apple's instructions for hula dancing are paltry at best, but if you look carefully you'll find the proper steps. Google is your friend.
I've had pretty good success by not having excess provisioning profiles in either Xcode or my test devices, only the bare minimum. Then I have gotten reallllllllly retentive about making sure that both the project and target build settings are set for the RELEASE configuration -- the build configuration you see when you get-info often isn't what you have set in XCode so I've horsed around changing provisioning profiles for the wrong configuration and then wondering why release didn't work.
And my hula dance is only invoked after an upload failure... the steps are:
* delete provisioning profiles from Xcode
* get a new, fresh profile from Apple (I don't always do this on the first round)
* drag new profile to XCode
* reset the provisioning profiles for both the project and target
* clean all targets
* quit XCode
* shutdown
* before restart, kneel in front of computer and bow thrice saying "oh, mighty machine". Both hands must be raised in the air held shoulder width apart. <-- crucial step, do not omit, alter or otherwise modify
* restart, relaunch, build (not build and go!), verify mobile provisioning is in the package, compress, upload, and rejoice.
* cross fingers and hit CONTINUE.
in the rare instances where it fails again, I remember that this is software just like Windows is software... and I repeat the dance.
