团队代理是唯一可以构建 Ad Hoc 的代理吗?

发布于 2024-10-07 09:08:17 字数 429 浏览 8 评论 0原文

首先介绍一点背景。我正在为客户构建移动应用程序,该客户当前拥有他们希望从中分发应用程序的开发人员帐户。以前,我一直使用自己的开发者帐户来构建临时版本,以将里程碑版本发送给客户。我们现在已经接近交付,我已经开始将构建转移到使用客户的凭据。

老实说,这是我第一次在自己的开发者帐户中开发应用程序,因此即使设置开发证书/配置也需要解决一些问题。具体来说,我无法使用他们现有的开发人员证书,而是使用我在我的计算机上创建、上传并获得他们批准的证书。没关系,我现在正在本地构建到我的设备。

然而,(这是我的问题)我在为他们设置临时分发时遇到了问题。也就是说,安装他们的临时证书似乎不起作用。我的假设是这是因为它不是在我的机器上构建的。但是,没有任何设施作为非团队代理来创建我自己的临时证书。

是否只有团队代理才能从他们的机器上进行临时(我假设提交构建)?作为团队成员,我是否无法从我的开发机器上进行临时构建?

First a little background. I am building a mobile app for a client, this client currently owns the developer account they wish to distribute the application from. Previously, I had been using my own developer account to build ad hoc to send milestone builds to the client. We are now getting close to ship and I have begun transferring the build to using the client's credentials.

Honestly, this is the first time I've worked on an app that was in my own developer account, so even setting up the dev cert/provisioning took some trouble shooting. Specifically, I couldn't use their existing developer certificate, but one that I created on my machine, uploaded and they approved. That's fine, I'm building locally to my device now.

However, (and here's my question) I ran into problems setting it up for them to do ad hoc distributions. Namely, installing their ad hoc certificate doesn't seem to work. My assumption is that it is because it wasn't build on my machine. However, there is no facility as a non-team agent to create my own Ad Hoc certificate.

Is it the case that only team agents can do Ad Hoc (and I'm assuming submission builds) from their machine? Is there no way that I as a Team Member can do an ad hoc build from my development machine?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

余生再见 2024-10-14 09:08:17

当您在钥匙串实用程序中生成签名请求(生成临时配置文件的第一步)时,它会同时生成私钥并将其保存到您的钥匙串中。如果您的 Mac 上的钥匙串中有该私钥,则只能根据 Ad Hoc 配置文件进行构建。

所以你的解决方案是

  1. 让他们从钥匙串中导出他们的私钥并发送给你。然后将其导入到您的钥匙串中。他们还应该向您发送他们创建的临时移动配置文件。您将其拖放到 xcode 上。

  2. 在您的计算机上生成签名请求,并将其发送给他们以生成新的临时配置文件,该配置文件仅适用于您的 Mac(不过,您可以再次向他们发送私钥)。

  3. 最后一个选项是将源代码发送给他们以编译 Ad Hoc 构建。

When you generate a signing request in Keychain Utility (the first step of generating an Ad Hoc profile), it simultaneous generates a private key and saves it to your keychain. You can only build against the Ad Hoc provisioning profile if you have that private key in the Keychain on your Mac.

So your solutions are

  1. Get them to export their private key from the keychain and send it to you. You then import it into your keychain. They should also send you the Ad Hoc mobileprovisioning file they created. You drag and drop this onto xcode.

  2. Generate the signing request on your machine, and send it to them to generate a new Ad Hoc profile which will then only work on your Mac (though again, you could send them the private key).

  3. The final option would be to send the source code to them to compile the Ad Hoc builds.

过期以后 2024-10-14 09:08:17

配置门户分发方法明确指出:

只有团队代理有权
准备并提交申请
分布。

团队代理也是唯一有权创建临时分发配置文件的人。

但是,一旦创建了分发配置文件,团队代理应该能够下载它并将其交给您以创建临时分发版本。

The Provisioning Portal Distribution How-To explicitly states:

Only Team Agents are authorized to
prepare and submit applications for
distribution.

Team Agents are also the only ones authorized to create an Ad-Hoc distribution profile.

However, once the distribution profile is created, the Team Agent should be able to download it and hand it off to you for creating Ad-Hoc distribution builds.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文