简体   繁体   English

代码签名下的配置文件和用于.ipa文件签名的配置文件

[英]Provisioning profile under code signing and provisioning profile for signing .ipa file

I am so much confused provisioning profiles that comes under Build Settings->Code Signing Identity and provisioning profile used for signing .ipa file. 我对用于“ .ipa”文件Build Settings->Code Signing Identity和供应配置文件下的供应配置文件感到非常困惑。

Should I always use same provisioning profile for both? 我是否应该始终对两者使用相同的配置文件?

If I select one Adhoc provisioning profile to sign .ipa file then how does the provisioning profile under Build Settings->Code Signing Identity matters/affect the build? 如果我选择一个Adhoc provisioning profile来签名.ipa文件,那么“ Build Settings->Code Signing Identity下的供应配置文件如何影响/影响构建?

I am more unclear about the provisioning profile under Build Settings->Code Signing Identity . 我对“ Build Settings->Code Signing Identity下的供应配置文件不清楚。

Lastly, if I set provisioning profile under Build Settings->Code Signing Identity to Distribution profile and sign .ipa with Adhoc provisioning profile then should it work? 最后,如果我将“ Build Settings->Code Signing Identity下的供应配置文件Build Settings->Code Signing Identity为“ Distribution profile并使用Adhoc provisioning profile .ipa进行签名,那么它是否可以工作?

If I select one Adhoc provisioning profile to sign .ipa file then how does the provisioning profile under Build Settings->Code Signing Identity matters/affect the build? 如果我选择一个Adhoc供应配置文件来签名.ipa文件,那么“构建设置”->“代码签名身份”下的供应配置文件如何影响/影响构建?

I think there is no difference how to sign the app: during the build process from Build Settings->Code Signing Identity or after building when you create the .ipa file. 我认为如何对应用程序进行签名没有区别:在“构建设置”->“代码签名身份”的构建过程中,或者在构建.ipa文件时进行构建之后。 In case you re-sign the app under creating the .ipa, you will rewrite the information in app packatge to use new provision profile so the previous sign action will be no longer actual. 如果您在创建.ipa时对应用程序进行了重新签名,则将重写应用程序包中的信息以使用新的配置文件,因此以前的签名操作将不再可行。

Lastly, if I set provisioning profile under Build Settings->Code Signing Identity to Distribution profile and sign .ipa with Adhoc provisioning profile then should it work? 最后,如果我将“构建设置”->“代码签名身份”下的供应配置文件设置为“分发”配置文件,并使用Adhoc供应配置文件对.ipa进行签名,那么它应该可以工作吗?

Thus yes, it should work (If correctly understand the question). 因此,是的,它应该起作用(如果正确理解了问题)。 However, there are some limitations of Development/Distribution profiles. 但是,开发/分发配置文件存在一些限制。 Maybe, following links will be helpful: 也许以下链接会有所帮助:

What is the difference between a development provisionong profile and a ad hoc distribution profile? 开发配置文件概要和临时分发概要之间有什么区别?

What is difference between .ipa with development provisioning and .ipa with adhoc distribution provisioning profile? 具有开发配置的.ipa与具有临时发行配置文件的.ipa有什么区别?

iOS Developer Builds vs Distribution Builds iOS开发人员内部版本与发行版本内部版本

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 使用过期的配置文件和有效的证书重新签署ipa - Re-signing ipa with expired provisioning profile and with a valid certificate 未在配置文件中签名应用程序的.extension - Signing .extension of app not in provisioning profile 代码签名错误:配置文件 ***** 不包括签名证书 **** - Code Signing Error: Provisioning profile ***** doesn't include signing certificate **** 开发配置文件的通配符应用程序ID /“未找到代码签名标识” - Wildcard App ID for Developement Provisioning Profile/“No Code Signing Identity Found” 有没有办法以编程方式获取应用程序的当前代码签名身份和/或配置文件? - Is there a way to programatically get the current Code Signing Identity and/or Provisioning Profile of an app? 存档错误[供应配置文件,应用程序ID和代码签名] - Archive Errors [Provisioning Profile, App ID, and code Signing] “ iPhone Developer”与供应配置文件代码签名身份 - “iPhone Developer” vs. provisioning profile code signing identity 无效的配置文件 - 缺少代码签名证书 - Invalid Provisioning Profile- Missing Code-Signing Certificate 代码签名过程中配置文件会发生什么变化? - What happens to the provisioning profile during the code signing process? 在Xcode“代码签名”构建设置中配置“供应配置文件”选项 - Configuring “Provisioning Profile” option in Xcode “Code Signing” build settings
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM