为客户、我们的开发帐户构建应用程序或设置它们？
我仍在努力解决这个问题。到目前为止，我们已经在单一开发人员许可证下为自己制作了内部应用程序，但现在我们的一些客户正在请求应用程序。
如果我错了，请纠正我，但有两种方法可以解决这个问题。
应用程序是在我们的开发帐户下为客户开发的，客户相信我们会向他们发送销售趋势以及来自应用程序的任何收入。客户无法访问 iTunes Connect（因为我们所有其他应用程序都在那里）。
我们让客户在 Apple 创建自己的开发者帐户，设置自己的银行业务，然后向我们发送团队负责人的登录详细信息，以便我们可以根据他们的详细信息生成应用程序。我想这里必须接受一定程度的信任，因为我们可以看到客户银行详细信息以及可能他们原始的 iTunes 登录详细信息？我还认为，我们应该专门为每个客户项目设置不同的工作站登录，以便任何钥匙串数据都与其他帐户分开。
我做对了吗？
非常感谢您的帮助。
杰夫
I am still trying to get my head around this. So far we have produced in house apps for ourselves under a single developer licence but now some of our clients are requesting apps.
Correct me if I am wrong but there are two ways to approach this.
App is developed under our dev account for the client, client trusts us to send them sales trends and any income from their apps. Client has no access to iTunes Connect (as all our other apps are on there).
We get the client to create their own Developer Account with Apple, setup their own banking then send us the team leader login details so that we can produce apps under their details. I imagine some amount of trust has to be accepted here as we can see the client banking details and possibly their original iTunes login details? I also imagine that we should setup different workstation logins specifically for each client project so that any keychain data is kept separate from other accounts.
Have I got this right?
Many thanks for help.
Geoff
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
是的，对我来说听起来不错，但如果客户端可以为您提供配置文件，您将不需要登录详细信息。恕我直言，你的选项 1 实际上是不可行的。
当然，还有可能满足您需求的 B2B Apple 计划：
http://images。 apple.com/business/docs/ASVPP_Business_Guide_US.pdf
“企业可以与第三方应用开发商和业务合作伙伴合作，通过该计划安全、私密地采购这些定制 B2B 应用。”
Yes, sounds right to me, except you won't need the login details if the client can provide you with the provisioning profiles. Your option 1 wouldn't realistically be feasible imho.
Of course there is also the B2B Apple program which might fit your needs:
http://images.apple.com/business/docs/ASVPP_Business_Guide_US.pdf
"Businesses can work with third-party app developers and business partners to procure these custom B2B apps securely and privately through the program."
选项 1 是最乏味的，因为这意味着您必须每周在电子表格中列出他们的利润。与谷歌等公司相比，苹果的销售报告页面出奇地简单，所以我认为这会给你带来一些痛苦，让你想知道为什么我们要这样做。
选项 3 怎么样，您向他们发送源代码并让他们的 iOS 人员（假设他们有）构建并分发二进制文件？
Option 1 would be most tedious because it would mean that you have to tabulate their profits for them on a weekly basis in a spreadsheet. Apple's sales reporting pages are surprisingly simplistic as compared to e.g. Google's so I think this would give you some agony and make you wonder why why why are we doing it this way.
How about an Option 3, in which you send them the source code and have their iOS person (assuming they have one) build and distribute the binary?
最好的选择是都有各自的苹果开发者帐户。
使用您的帐户创建 xarchive 并将其发送给客户，客户可以使用其签名者（证书和配置文件）从 xarchive 中制作 ipa
仅供参考：
让客户知道您的捆绑包 ID 和应用程序的权利，以便他们可以在其会员中心帐户中创建匹配的配置文件。
并要求他们手动更改 entitlements.plist 中应用程序标识符中找到的团队 ID
Best option is both have their individual apple developer accounts.
Make an xarchive using your account and send that to client and client can make ipa out of xarchive with their signers(cert and provisioning profile)
FYI:
Let the client know your bundle id and entitlements of the app so that they can create matching provisioning profile in their member center account.
and ask them to change the team id found in application identitifer in entitlements.plist manualy