Reputation: 1188
After updating to the latest build of Xcode 7.3 (7D175), every time I try to Export for adhoc distribution I get the above error. Everything was working fine up until the update. The bundle ID is definitely my own, registered to this application. I've tried recreating my certificates, provisioning profiles, deleting old ones, frantically clicking the 'try again' button ... nothing seems to work.
Any one find a solution to this? I saw some others were facing the same problem, but none of their solution seem to work for me (https://stackoverflow.com/a/36192586/1542275, https://stackoverflow.com/a/36175175/1542275)
update: I'm not sure if this is relevant, but for the heck of it I tried to 'validate' the build. I did and it passed. Anyway, just before you fire off the validation you get the information screen that shows you all the details about the attached prov-profile. I noticed that despite selecting my adhoc prov-profile, the information screen (just before validating) said that it was using my distribution profile. I then removed my distribution profile from xcode, re-archived, and now validation is failing. Something weird seems to be going on with archiving, adhoc, and exporting.
Upvotes: 28
Views: 39013
Reputation: 363
In my case nothing from above worked until I tried changing my bundle identifier prefix from
com.xxx.NameOfMyApp to com.xxxYYY.NameOfMyApp.
I must have accidentally picked a prefix someone else had already used.
Upvotes: 0
Reputation: 11
I had the same error with my Ionic project when I imported it to Xcode. I had right team selected and right bundle identifier mentioned in the General Tab of the Target (the same team and identifier I had used in App Store to register)as shown in this picture . I had all the certificates/provisioning profiles downloaded needed for the project. Yet it complained.
How I solved it?
I checked the Code Signing section in the Build Settings of the Target. Please click here to see. In the Code Signing Identity area, I saw, the Xcode automatically selected iOS Distribution for all section of that area. I then, changed the value for the Debug and Release section to the identity that contained my Team Id. And it worked. All the errors were gone!!!
In my case, the problem was that the Xcode used to generate its own Team Id (XC) in the previous cases.
You might also have to manually select the Provisioning Profile too (just in case if the Xcode selects wrong profile)
I hope this helps someone.
Upvotes: 0
Reputation: 582
I only had to change the provisioning profile to a different one. I had made one of each type: Development, Ad Hoc Distribution, and Store Distribution.
Once I changed to Development, the error went away. Seems so simple. But sometimes it is simple, Thanks to God. LOL.
Upvotes: 0
Reputation: 328
Just need to add prefix in your app id
Ex:
it should be KMW5E9785J.com.myapp.app in your Bundle identifier in info.plist
So No need to change XC or anything from your dev portal
Upvotes: 1
Reputation: 529
I had this problem with a project that I've been working on for years, using Xcode 7.3. But one of my colleagues, who cloned the same Xcode project, doesn't have this problem. After trying several different approaches, I downloaded the development certificate from Apple Developer and installed them manually. It works all of a sudden. My guess is Xcode 7.3 messed up with the automatic "fix the problem" feature.
Upvotes: 0
Reputation: 1619
I can see lot's of great answers,
I tried a few of them but no luck, finally I used "Use local signing assets" option to export ipa and it works for me.
Hopefully this will help someone.
Upvotes: 1
Reputation: 1460
Nothing was working for me in Xcode 7.3. This can save you a lot of time, I solved it this way:
Xcode -> Preferences -> Accounts -> Provisioning Profiles -> Right Click them and move them to trash. Quit Xcode.
Member Center -> Provisioning Profiles -> All -> Deleted everything here (I have a single iOS app). Created a fresh new Profile with my app ID.
Member Center -> App IDs -> My App ID was of the form
Xcode iOS App ID com myDomain myApp
. If this is your case, blindly follow along -> Edit it, and try renaming it to the form
XC com myDomain myApp
-> if it says "Enter a valid name" in red, be patient a drop down will appear if your cursor is inside the Name text field - choose it and click Save. [Don't ask what's going on here, it just works - we have better things to deal with]
Upvotes: 1
Reputation: 1402
Sometimes after you click on Export the selected Team doesn't match the one in the certificate. You should check that the selected Team is correct if you have multiple teams on the same machine.
Upvotes: 1
Reputation: 736
I was getting this error using Xcode 7.3.1. The cause was using the wrong "Team" on the General tab of the main target. I had my company's Team, and my own AppleID that was a "Free" personal account. After I switched to my company's Team, the error went away.
Upvotes: 2
Reputation: 2158
I just installed Xcode 7.2.1 and could successfully export AdHoc build with it. While Xcode 7.3 keeps on telling that there is something wrong with bundle identifier.
UPDATE:
Looks like changing the "Name" (not the ID) of App ID in developer portal under "Certificates, Identifiers & Profiles" to the next format "XC com mycompany appname" (in case your app ID was com.mycompany.appname) helps Xcode see your appID. Strange but it's working.
Upvotes: 51
Reputation: 1
I encountered the same problem, I solved it. Validate required appstore certificate. Adhoc and Validate require different certificate.
Upvotes: 0
Reputation: 11
i just resolve the problem by delete the Xcode account Provisioning Profiles.and download again. xcode account details
Upvotes: 0
Reputation: 1188
OK - I may have a solution. Though you won't like it because it is a major pain. I went to Apple members center, deleted all of my certs all of my profiles and started from scratch.
I wish I had solid steps to give you to follow but I did so much that I'd honestly just be guessing. In the end here is what I'd suggest:
I'm now able to create adhoc builds and export them using xcode 7.3.
All of that said, do this with the intention to get into some BS. It took me a long time to get things set up and working again. From re-creating all of the above to countless device, xcode, and computer restarts.
Now a new issue has come up - dyld: Library not loaded: @rpath/
regarding one of my swift cocoapods ... so more fun. What a wasted day :(
Upvotes: 5