Xcode托管配置文件设置的Azure Piplines配置-可能吗?有记录吗? [英] Azure Piplines Configuration for Xcode Managed Profile Setup - Possible? Documented?

查看:82
本文介绍了Xcode托管配置文件设置的Azure Piplines配置-可能吗?有记录吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

环境

Server - Azure Pipelines
Hosted MacOS agent

问题说明

我在Xcode项目中使用以下配置(带有自动代码签名):

I'm using the following configuration in my Xcode project (w automatic code signing):

如果我在构建之前已在管道中手动安装了所有配置概要文件和证书,是否可以使用此配置来构建管道并签署项目?

Is it possible to have Pipelines build and sign a project using this configuration if I've manually installed all of the provisioning profiles and certs in my pipeline prior to building?

该场景是否有任何文档或操作指南?或者,如果无法做到这一点,那么也许可以就此发表明确的声明,并就下一步可以尝试的建议提供建议.例如-我需要将该项目从自动签名的项目转换为手动的项目吗?

Is there any documentation for this scenario or a how-to guide? Alternatively, if this is not possible perhaps a definitive statement on this and advice on what to try next in order to work. For instance - do I need to convert this project from an automatically signed one to a manual one?

我正在使用以下页面,其中提到了自动签名,但未提供有关如何配置的任何说明(但确实提到了此选项):

I'm using the following page which mentions automatic signing but doesn't give any instructions on how to configure (but does mention this as an option):

https://docs.microsoft.com/zh-cn/azure/devops/pipelines/apps/mobile/app-signing?view=vsts&tabs=apple-install-during-build

任何帮助将不胜感激.

谢谢

安德鲁

推荐答案

以帮助以后遇到此问题的任何人.

To help anyone who comes across this later.

我的问题是我有一个具有多个目标(应用程序,窗口小部件,Siri Intent和Siri UI)的解决方案.这些中的每一个都需要它自己的配置文件,并且需要独立签名-这是我遇到的麻烦(默认配置似乎试图在签名时尝试将App配置文件应用于所有目标).

The issue in my case was that I have a solution with multiple targets (App, Widget, Siri Intent, and Siri UI). Each of these requires it's own provisioning profile and needs to be signed independently - this is where I ran into trouble (the default configuration seemed to try and apply the App profile to all Targets when signing).

为了帮助任何对此感到困惑的人-为了解决这一问题,我需要在Xcode中执行以下步骤:

To help anyone who struggles with this - in order to solve I needed the following steps in Xcode:

  1. 将项目转换为手动签名.
  2. 以Xcode存档和导出
  3. 通过App Store分发"
  4. 选择导出但不提交并选择位置
  5. 为导出选择了所需的配置文件.
  6. 导出后,转到保存的位置并抓取"exportOptions.Plist".
  7. 在相应的DevOps中为导出选项"选择.plist 管道.
  1. Convert the project to manual signing.
  2. Archive and export in Xcode
  3. 'Distribute via App Store'
  4. Select to Export but not submit and choose a location
  5. Selected the desired provisioning profiles for the export.
  6. After export head to saved location and grab 'exportOptions.Plist'.
  7. Choose .plist for 'export options' in the appropriate DevOps pipeline.

Voila,您可以使用多种方案签署解决方案!

Voila you can sign your solution with multiple schemes!

希望这对某人有帮助.

安德鲁

PS-稍后,我将确认将一切设置回自动签名都可以通过exportOptions.Plist进行工作,并将进行报告.

PS - At some moment I will confirm that setting everything back to automatic signing works with exportOptions.Plist and will report back.

这篇关于Xcode托管配置文件设置的Azure Piplines配置-可能吗?有记录吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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