XCode 运行配置文件/检查器的配置配置文件无效 - iPhone 应用程序

发布于 2024-11-27 14:53:31 字数 246 浏览 6 评论 0原文

当我执行“命令 I”或 XCode 产品菜单并选择配置文件菜单项时,显示“未找到此可执行文件的有效配置文件”。

我想分析我的 iPhone 应用程序是否存在内存泄漏。我有一个有效的团队配置文件,并且有一个有效的应用程序特定配置文件和分发配置文件。

我必须在构建设置中设置一些东西,但我无法弄清楚。搜索无效的配置文件进行分析时,其中包含太多配置文件单词,但我没有找到任何内容。

我不想打扰大家,但我不知道如何寻找解决方案或找到答案。

"A valid provisioning profile for this executable was not found" is displayed when I do a "command I" or XCode Product Menu and select the Profile menu item.

I want to profile my iPhone application for memory leaks. I have a valid team provision profile and I have a valid app specific provisioning profile and distribution profile.

I must need to setup something in the build settings but I can't figure it out. Searching for invalid provisioning profile for profiling has too many profile words in it and I don't find anything.

I hate to bother everyone, but I am out of ideas on how to search for a solution or find the answer.

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

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

发布评论

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

评论(1

脱离于你 2024-12-04 14:53:31

根据我的经验,如何设置配置设置的最安全方法如下:

  1. 转到“项目构建设置”选项卡(在目标上方,其中
    您设置了代码签名)
  2. 将“不要代码签名”设置为所有字段,这是为了确保您不会遇到任何麻烦
    未来。这给我在提交应用程序时带来了很多麻烦
    过去
  3. 转到您的目标“构建设置”选项卡
  4. 将调试(父级调试及其任何 iOS SDK 子级)设置为“iPhone 开发人员”
    这是非常重要的,尤其是当你在团队中工作时。那里
    没有什么比有人建立自己的个人资料更糟糕的了
    提交到代码存储库!
  5. 按照您应该的方式静态设置您的生产/企业或临时配置
    控制用于任何配置文件的配置文件
    分布构建。

自从我改用这个之后,我从来没有遇到过构建不起作用、签名不正确或类似的问题!

此外,我第一次连接到任何机器的每台设备都会通过“+”(加号)按钮添加到开发人员门户,以确保设备和 Mac 都具有最新的配置!

Most secure way how to setup your provisioning settings from my experience is as follows:

  1. Go to the Project build settings tabs (above your targets where
    you set your code signing)
  2. Set "Don't code sign" to all the fields, this is to make sure you not going to run into any trouble in
    the future. This has cased me a lot of trouble during app submissions
    in the past
  3. Go to your targets Build settings tab
  4. Set both debug (Parent Debug and it's Any iOS SDK child to "iPhone developer"
    this is extremely important especially if you work in a team. There
    is nothing worse than someone setting up their own profile and than
    committing to the code repository!
  5. Set provisioning for your Production / Enterprise or AdHoc statically as you should be in
    control of what provisioning profile is being used for the any
    distribution build.

Since I have switched to this, I never had a problem with a build that didn't work, was incorrectly signed or similar!

Also, every device I connect to any machine for the first time I add to the developer portal through the nice + (plus) button to make sure both device and Mac have the latest provisionings!

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