Xcode 6 beta 2 issue exporting .ipa: “Your account

2019-01-02 19:40发布

I'm having trouble exporting an app for Ad Hoc Distribution on Xcode 6 beta 2:

Failed to locate or generate matching signing assets

When exporting my project for ad hoc development on Xcode 6, I receive this alert. I've tried exporting it on Xcode 5 and had no problems at all saving the .ipa. Is anyone experiencing this problem as well?

27条回答
听够珍惜
2楼-- · 2019-01-02 19:58

There has been changes in way apple manages our private and public key. The previous method to share account on two machine was
1.download provisioning
2.export/checkout certificate

install them both on the other mac

but now you dont have to do that you export your entire account.
1.XCode -> preferences -> account (select account) on bottom left there is option to export thatenter image description here you will be prompted to give a password give any it will be required while importing on other system.A .developerprofile file will be downloaded on location of your choice.

2.download it on other mac and when you see the prompt your device already have valid signing identity click on import Developer Profile and import this .developerprofile file.enter image description here enter password when prompted.

got help from here

查看更多
浪荡孟婆
3楼-- · 2019-01-02 19:58

I revoke my producion certificates, and request another one, solve this problem. Maybe you need restart your xcode.

查看更多
不再属于我。
4楼-- · 2019-01-02 19:58

In my case, I got the error message when trying to export and AdHoc build from Organizer. I did two things, either of which may have fixed the issue:

1) Exported the existing certificate it claimed I did not have from my keychain, deleted it from keychain, re-imported.

2) Created an ad-hoc distribution certificate, refreshed XCode account to obtain the new distribution provisioning profile.

After that I was able to export the exact same archive to an AdHoc build. I really think it was only that fact I was missing an ad-hoc distribution that targeted that specifc bundleID that led to XCode being confused.

Followup: The archive I had created before did not work, I had to re-generate it. A clue this was an issue was that when selecting the archive and opting to export an Ad-Hoc build, the default account selected was the wrong account for the build (the project had no default account selected when I archived the build).

查看更多
无色无味的生活
5楼-- · 2019-01-02 19:59

I had the same problem, I had to use the command line "xcodebuild" tool as a workaround, with only Xcode 6 installed (didn't have to re-install Xcode 5).

http://www.thecave.com/2014/09/16/using-xcodebuild-to-export-a-ipa-from-an-archive/

Example:

xcodebuild -exportArchive -archivePath $projectname.xcarchive -exportPath $projectname -exportFormat ipa -exportProvisioningProfile "Provisioning Profile Name"
查看更多
梦寄多情
6楼-- · 2019-01-02 19:59

I just encountered this after upgrading from Xcode 5 to 6.

In my case creating a new production certificate and then recreating the distribution provisioning profile for my app did the trick.

查看更多
只靠听说
7楼-- · 2019-01-02 20:01

My Solution was Delete the only iOS Production Certificate which I'm using and create it again. Doing this, you must create a new Provisioning profile assigning the certificate just created.

then I did the process of Archive again and works!

查看更多
登录 后发表回答