没有可用的身份 - 管理员请求 [英] No identities were available - administrator request

查看:134
本文介绍了没有可用的身份 - 管理员请求的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在存档我的应​​用程序时遇到问题。我认为有无效的配置文件,因为iPhone更新到5.1和XCode更新到4.2.2。



我花了超过4小时摆脱认证问题而使用这个线程一步一步的3次(这花费了很多时间):




  • 前往 iOS Provisioning Portal - > 证书(左侧栏)>> 分发标签

  • 选中字段配置配置文件


  • 转到配置(左侧边栏) - > 分发选项卡。按新建配置文件并完成。


  • 在您的专案建置设定中,选取[新设定设定档](可能与旧设定档名称相同) li>

  • 在项目的构建设置中,将代码签名身份(所有人)更新为新身份(如果有的话)。 (旧的可能过期,这是您看到的错误消息的最大原因之一)


  • 验证您的包ID是否正确(CaSe SeNsEtIvE)


  • 返回XCode Organizer - 设备。单击TEAM(左侧栏),然后单击刷新(右下角)。你会发现XCode获取新的配置文件。如果加载了新内容,请重复步骤6和7(它们将被更改!)

    *如果您无法找到团队,因为您运行的是较新版本的xCode,请转到Xcode首选项(单击Xcode 在屏幕左上角的mac工具栏上),然后转到帐户,选择您的团队并单击刷新。如果加载了新内容,请重复步骤6和7(它们将被更改!)

    如果您位于偏好设置 - > 帐户 >仍然无法刷新,然后:




    • 点击帐户标签
    • >在列表中选择Apple ID
    • 点击右下角的查看详情

    • 点击左下角的刷新箭头

    • Xcode现在将刷新更新的凭据,您可以继续验证或分发您的应用程序。



  • 重新验证或分发您的应用程式。


  • 如果这不起作用,请转到项目设置>目标下的TEAM,然后选择无已选择无,您将需要重复步骤7并更改代码签名身份(所有这些),然后再次尝试归档。


  • 最后,以上工作。只需创建新的生产证书,并创建具有相同捆绑ID的新配置配置文件。 (是的,如果您正在更新已经上线的应用程式,这将有效)。下载证书和证书。配置文件并运行(双击)。现在重复步骤6并存档。这应该可以工作。



  • I had problems while "archiving" my app. I think there are invalid profiles because of iPhone Update to 5.1 and XCode update to 4.2.2.

    I've taken now more than 4 hours to get rid of certification issues while using this thread step by step 3 times (which costs a lot of time):

    Getting "A valid signing identity matching this profile could not be found in your keychain" warning

    I still have the following fault:

    No identities were available An administrator must request identities before they can be downloaded.

    The "Download identities" button went back to this window after processing some seconds.

    Do you know how to get out of this wood of certification documentations and solve that fault?

    解决方案

    1. Visit Member Center

    2. Go to "iOS Provisioning Portal" -> "Certificates" (Left sidebar) >> "Distribution" tab

    3. Check field "Provisioning Profiles". If empty, next (4)

    4. Go to "Provisioning" (Left sidebar) -> "Distribution" tab. Press "New Profile" and complete it. Go back to (3) check the field again.

    5. Download and "run" (double click) the new provisioning profile.

    6. In your project's build settings select the NEW provisioning profile (it might have the same name as the old one)

    7. In your project's build settings update your code signing identities (all of them) to the new one if there is one. (The old one was probably expired which is one of the biggest causes for the error message you saw)

    8. Verify that your bundle ID is correct (CaSe SeNsEtIvE)

    9. Back to XCode Organizer - Devices. Click TEAM (Left sidebar) and click "Refresh" (right-bottom). You will find XCode fetch the new profile. If new content loaded, repeat steps 6 and 7 (they will have been changed!)

      *If you can't find team because you are running a newer version of xCode, go to Xcode preferences (clicking "Xcode" on the mac toolbar on the top left corner of your screen) and go to account, select your team and click refresh. If new content loaded, repeat steps 6 and 7 (they will have been changed!)

      If you are in Preferences -> Accounts and you still can't refresh, then:

      • Click on the Accounts tab
      • Select an Apple ID in the list
      • Click "View Details" on the bottom right
      • Click on the refresh arrow on the bottom left
      • Xcode will now refresh the updated credentials, and you can proceed to validate or distribute your app.

    10. Validate or distribute your app again. It should work.

    11. If this didn't work then go to "TEAM" under project settings > targets and select "none"... Now that you have selected None you will need to repeat step 7 and change the code signing identities (all of them) and try archiving again.

    12. Lastly, if none of the above worked. Simply create a new production certificate AND create a new provisioning profile with the same bundle ID. (Yes, this will work if you are updating an app that is already live). Download the cert and prov. profile and run both (double click). Now repeat step 6 and archive. This should work.

    这篇关于没有可用的身份 - 管理员请求的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

    查看全文
    登录 关闭
    扫码关注1秒登录
    发送“验证码”获取 | 15天全站免登陆