关于iPhone / iPad辞职的非常棘手的问题构建行为 [英] Very tricky question about iPhone/iPad resigned builds behaviors
问题描述
这就是事情......
Here's the thing..
场景：
我有一个ipa文件，我得到的是存档+共享流程的结果
使用XCode。 ipa文件使用临时分发证书进行签名，
可以毫无问题地安装。
I got a ipa file which I get as a result of an Archive + Share process using XCode. The ipa file is signed using ad hoc distribution certificates and it can be installed without any problems.
应用程序将一些信息保存在钥匙串中
使用我刚刚制作的版本访问时没有任何问题。
The application saves some information in the keychain which is accessed without any problems using the build I just made.
之后，我使用带有Enterprise
分发证书的codesign命令重新签名应用程序在applyaction.app包中进行一些更改。
此更改包括更改
info.plist文件中的应用程序名称和捆绑ID，当然，将
替换嵌入式移动配置文件与新证书匹配。
After that, I re-sign the application using the codesign command with Enterprise distribution certificate after making some changes in the applicaction.app package. This changes includes changing the name of the application and bundle id from the info.plist file, and of course, replace the embedded mobile provisioning profile with the one that matches the new certificate.
问题：
辞职后似乎没事，安装和功能似乎都可以正常工作。 ......但是！当我输入保存在钥匙串中的信息
时，每次关闭应用程序时，数据似乎都不会加载或从
钥匙串中擦除。
After resigning every seems to be all right, installation and functionality seems to work ok.... BUT! when I enter the information that is saved in the keychain, the data seems not to load or be wiped from the keychain every time I close the app.
为什么会发生这种情况的想法？
Ideas of why is this happening?
推荐答案
好的，这是适用于我们的解决方案。
Ok, here's the solution that worked for us.
由于这是一个企业版本，它要求我们更改Entitlements.plist / dist.plist文件，以便app app与Apple网站上输入的内容相匹配。可以在codesign实用程序上提供Entitlements文件。
Since this was an Enterprise build, it required us to change the Entitlements.plist/dist.plist file so that the app id matched what was entered on Apple's site. The Entitlements file can be provided on the codesign utility.
使用这些说明，但验证Entitlements文件是否与完整的应用ID相匹配。这包括种子ID +包ID。
Use these instructions but verify the Entitlements file matches the full app id. This includes the seed id + bundle id.
如果没有它，应用程序将安装正常，但这可确保使用适当的权限访问密钥库。
The app would install fine without it, but this ensures the keystore is being accessed with the proper authority.
这篇关于关于iPhone / iPad辞职的非常棘手的问题构建行为的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
