意外的 CFBundleExecutable 键 [英] Unexpected CFBundleExecutable key

查看:23
本文介绍了意外的 CFBundleExecutable 键的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在谷歌上搜索了一段时间后,我发现问题是新的.

After spending some time googling, something tells me that the issue is new.

我们有一个支持 iOS7-8 的全功能项目.当然是多次成功提交到AppStore.

We had a fully functional project supporting iOS7-8. Of course it was multiple times successfully submitted to AppStore.

我们使用 pod,进行大量跟踪和监控,例如 GA 和 Instabug.

We use pods, lots of tracking and monitoring, like GA and Instabug.

现在我们决定向 TestFlight 提交一个基于 Xcode 7 和 iOS 9 构建的应用版本.

Now we decided to submit a version of the app built on Xcode 7 on iOS 9 to TestFlight.

我们禁用了 bitcode,因为许多 pod,如 Flurry 和其他预建库都不包含它.

We disabled bitcode, since many pods, like Flurry and other prebuilt libraries does not include it.

构建成功,提交到 iTunesConnect 后我们得到:

The build was successful, after the submission to iTunesConnect we get this:

我们有同样的 GoogleAppIndexing 库(也在 pod 中),但我们删除了它,只是为了让它工作.现在 - Instabug.它走得太远了,所以我试图了解 iOS 9 中发生了什么,以及哪些更改使一个完全正常工作的项目开始抛出此类错误.

We had same for GoogleAppIndexing library (in pods too), but we removed it, just to make it work. Now - Instabug. It is going too far, so I am trying to understand what is going on in iOS 9 and what are the changes that made a fully working project to start throwing such errors.

欢迎任何想法和想法!请分享您的经验,如果我错过了什么,我很乐意分享我的步骤.

Any thoughts and ideas are welcomed! Please share your experience, and if I missed something, I will gladly share my steps.

推荐答案

今天我在尝试提交我们的应用程序(使用 Xcode 7 beta 5)但不是 instabug 时遇到了同样的问题,并出现了完全相同的错误消息.bundle 位,这是给我的TencentOpenApi_IOS_Bundle.bundle.

I encountered the same problem today with the same exact error message when trying to submit our app (using Xcode 7 beta 5) but instead of the instabug.bundle bit, it was for me TencentOpenApi_IOS_Bundle.bundle.

我通过在项目中找到命名包解决了这个问题 - 正如错误消息所暗示的 - 通过删除 CFBundleExecutable 编辑了包中的 Info.plist代码>键.CFBundlePackageType 键已经设置为 BNDL 所以我没有碰它.

I solved the problem by finding the named bundle in the project then - just as the error message suggests - edited the Info.plist that is in the bundle by removing the CFBundleExecutable key. The CFBundlePackageType key was already set to BNDL so I didn't touch it.

在这些更改之后,我做了 Product > Clean,然后将应用程序提交到 App Store 没有问题.

After these changes I did Product > Clean and then had no problem submitting the app to the App store.

我希望这会有所帮助.

这篇关于意外的 CFBundleExecutable 键的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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