ios Apple Developer - 显示无效状态的配置文件
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/25887845/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Apple Developer - Provisioning profile showing invalid status
提问by Ankur Loriya
I am new in ios, I have created provisioning profile on developer.apple.com more than 6 months ago.
我是 ios 新手,6 个多月前我在 developer.apple.com 上创建了配置文件。
Today I checked profile it showing invalid status.
今天我检查了显示无效状态的配置文件。
Any suggestion what happing with provisioning profile?
对配置文件有什么建议吗?
回答by VJ Vélan Solutions
May be you added a new device to the mix or updated something else that affects this mobileprovision
. Click on the Edit
and just re-generate the mobileprovision
and the status should then go from Invalid
to Green dot that is Valid
可能是您添加了新设备或更新了其他影响此的设备mobileprovision
。单击Edit
并重新生成,mobileprovision
然后状态应该从Invalid
绿色点变为Valid
回答by ABHIJEET RAVI
Q: What causes the provisioning profile "Invalid" status? How do I resolve it, and how do I prevent it?
问:是什么导致配置文件“无效”状态?我该如何解决,又该如何预防?
A: The provisioning profile invalid status is caused by changes to the profile's associated certificate or App ID. Any time an App ID or certificate changes, all profiles that are associated to it are marked Invalid. This does not apply to Xcode's team profiles, but applies to all profiles that Xcode does not manage, specifically, custom development profiles and distribution profiles. This document explains the causes in detail and provides steps to resolve and avoid the profile invalid status.
A:Provisioning Profile 无效状态是由配置文件的关联证书或 App ID 的更改引起的。每当 App ID 或证书发生更改时,与其关联的所有配置文件都会标记为无效。这不适用于 Xcode 的团队配置文件,但适用于 Xcode 不管理的所有配置文件,特别是自定义开发配置文件和分发配置文件。本文档详细解释了原因,并提供了解决和避免配置文件无效状态的步骤。
The provisioning profile lives for 1 year, maybe it expired so simply remove it and make another one with the same certificates, app ids and devices and you can use it without any problem.
配置文件的有效期为 1 年,也许它已过期,因此只需将其删除并使用相同的证书、应用程序 ID 和设备创建另一个配置文件,您就可以毫无问题地使用它。
If you generate a new provisioning profile, your old installations (store or adhoc) won't be affected
如果您生成新的配置文件,您的旧安装(商店或临时)不会受到影响
回答by Lokendra Chouhan
I was struggling with this today, it was super frustrating. For now, just go into "File" > "Project Settings..." (or in some cases "Workspace Settings...") and then select "Legacy Build System" from the "Build System" dropdown.
我今天正在为此苦苦挣扎,这非常令人沮丧。现在,只需进入“文件”>“项目设置...”(或在某些情况下“工作区设置...”),然后从“构建系统”下拉列表中选择“传统构建系统”。
回答by jafarbtech
In my case I have changed my Identifier Name
after creating the provisional profile. That's why it was showing Invalid
.
在我的情况下,我Identifier Name
在创建临时配置文件后更改了我的。这就是为什么它显示Invalid
.
I just clicked the provisional profile which was showing Invalid
and clicked the Edit
and Save
button without changing anything. Then it became Valid
and showed the expiration date. Now I downloaded the new file once again
我只是单击了显示的临时配置文件,Invalid
然后单击了Edit
和Save
按钮而没有更改任何内容。然后它变成Valid
并显示了有效期。现在我再次下载了新文件