ITMS-90535 无法使用最新的 Google Signin SDK 发布 iOS 应用程序
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/32622899/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
ITMS-90535 Unable to publish iOS app with latest Google Signin SDK
提问by Guy
I'm using xcode 7 GM seed and installed latest Google Signin SDK through cocoapods pod "Google/SignIn
. I get the attached error when I try to publish my app to apple app store.
我正在使用 xcode 7 GM 种子并通过 cocoapods 安装了最新的 Google Signin SDK pod "Google/SignIn
。当我尝试将我的应用发布到苹果应用商店时,我收到了附加的错误。
Help!!
帮助!!
Here are the detailed versions of Google SDK pods
以下是 Google SDK pod 的详细版本
- Google/Core (1.0.7):
- GoogleNetworkingUtilities (~> 1.0)
- GoogleSymbolUtilities (~> 1.0)
- GoogleUtilities (~> 1.0)
- Google/SignIn (1.0.7):
- Google/Core
- GoogleSignIn (~> 2.0)
- GoogleAppUtilities (1.0.0):
- GoogleSymbolUtilities (~> 1.0)
- GoogleAuthUtilities (1.0.1):
- GoogleNetworkingUtilities (~> 1.0)
- GoogleSymbolUtilities (~> 1.0)
- GoogleNetworkingUtilities (1.0.0):
- GoogleSymbolUtilities (~> 1.0)
- GoogleSignIn (2.2.0):
- GoogleAppUtilities (~> 1)
- GoogleAuthUtilities (~> 1)
- GoogleNetworkingUtilities (~> 1)
- Google/Core (1.0.7):
- GoogleNetworkingUtilities (~> 1.0)
- GoogleSymbolUtilities (~> 1.0)
- GoogleUtilities (~> 1.0)
- Google/SignIn (1.0.7):
- Google/Core
- GoogleSignIn (~> 2.0)
- GoogleAppUtilities (1.0.0):
- GoogleSymbolUtilities (~> 1.0)
- GoogleAuthUtilities (1.0.1):
- GoogleNetworkingUtilities (~> 1.0)
- GoogleSymbolUtilities (~> 1.0)
- GoogleNetworkingUtilities (1.0.0):
- GoogleSymbolUtilities (~> 1.0)
- GoogleSignIn (2.2.0):
- GoogleAppUtilities (~> 1)
- GoogleAuthUtilities (~> 1)
- GoogleNetworkingUtilities (~> 1)
Thank you.
谢谢你。
回答by iHTCboy
Find CFBundleExecutable
key , remove this key from Google Signin SDK's info.plist.
You can delete all other CFBundleExecutable
if error occurs on multiple bundles
找到CFBundleExecutable
key ,从 Google Signin SDK 的 info.plist 中删除这个 key。CFBundleExecutable
如果多个捆绑包发生错误,您可以删除所有其他
回答by dstudeba
Just to clarify the above correct answer. If you are accessing the info.plist from Xcode, you need to clear the Executable file
field shown below.
只是为了澄清上述正确答案。如果您从 Xcode 访问 info.plist,则需要清除Executable file
下面显示的字段。
There is one in the GoogleSignIn/Resources folder, and the other two are in GPPCore/Resources folder. (click the .bundle)
一个在 GoogleSignIn/Resources 文件夹中,另外两个在 GPPCore/Resources 文件夹中。(单击 .bundle)
回答by Dasoga
回答by itzo
I am getting the same error with TapJoy Bundle Resources.
我在使用 TapJoy Bundle Resources 时遇到了同样的错误。
TapJoy is older version. So this problem is going to be fixed by either:
TapJoy 是旧版本。所以这个问题将通过以下任一方式解决:
- Update TapJoy SDK
- Remove the string from Executable fileof TapJoy's plist, not the app's plist just like user dstudeba suggested. In my case the String was TapJoyResourcesI removed that and worked perfect!
- 更新 TapJoy SDK
- 从TapJoy 的 plist 的可执行文件中删除字符串,而不是像用户 dstudeba 建议的应用程序的 plist。在我的情况下,字符串是TapJoyResources,我删除了它并且工作得很好!
Note: that plist was located at TapJoy's framework files. This error is exactly the same as with this Google Signin SDK issue.
注意:plist 位于 TapJoy 的框架文件中。此错误与此 Google Signin SDK 问题完全相同。
回答by Abdul Rauf
I have suffered from same error, above all answers really helped me. Want to share my experience.
我遇到了同样的错误,最重要的是答案真的帮助了我。想分享我的经验。
Fixed with the help of above answer
在上述答案的帮助下修复
Find CFBundleExecutable key , remove this key from Google Signin SDK's info.plist. You can delete all other CFBundleExecutable if error occurs on multiple bundles
找到 CFBundleExecutable 密钥,从 Google Signin SDK 的 info.plist 中删除此密钥。如果多个包发生错误,您可以删除所有其他 CFBundleExecutable
2- But after that, I was getting error
2-但在那之后,我遇到了错误
Xcode App Submisson ERROR ITMS-90207: "Invalid Bundle
Xcode 应用程序提交错误 ITMS-90207:“无效的捆绑包
Fixed with the help of answer
在回答的帮助下修复
Please check your info.plist file and add below key if not
请检查您的 info.plist 文件,如果没有,请添加以下键
<key>CFBundleExecutable</key>
<string>${EXECUTABLE_NAME}</string>
<key>CFBundleExecutable</key>
<string>${EXECUTABLE_NAME}</string>
回答by Maciej Stramski
We had this issue while uploading our build from jenkins slave. We managed to automate the process by adding this runs-script to pre-archive of our appstore scheme:
我们在从 jenkins slave 上传我们的构建时遇到了这个问题。我们通过将此运行脚本添加到我们的 appstore 方案的预存档中,成功地实现了该过程的自动化:
defaults delete "${PODS_ROOT}/google-plus-ios-sdk/google-plus-ios-sdk-1.7.1/GooglePlus.bundle/GPPCommonSharedResources.bundle/Info.plist" CFBundleExecutable
defaults delete "${PODS_ROOT}/google-plus-ios-sdk/google-plus-ios-sdk-1.7.1/GooglePlus.bundle/GPPShareboxSharedResources.bundle/Info.plist" CFBundleExecutable
defaults delete "${PODS_ROOT}/google-plus-ios-sdk/google-plus-ios-sdk-1.7.1/GooglePlus.bundle/Info.plist" CFBundleExecutable