ITMS-90535 Unable to publish iOS app with latest Google Signin SDK

Question

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 publi

Answer 1

I have suffered from same error, above all answers really helped me. Want to share my experience.

1- I was getting the error

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

2- But after that, I was getting error

Xcode App Submisson ERROR ITMS-90207: "Invalid Bundle

Fixed with the help of answer

Please check your info.plist file and add below key if not

<key>CFBundleExecutable</key> <string>${EXECUTABLE_NAME}</string>

Answer 2

I had to do this:

Delete 3 string values of 3 lines. info.plist from

1.GooglePlus.bunde -> Inside

2.GPPCommonSharedResources

3.GPPShareboxSharedResources

Answer 3

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

Answer 4

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:

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

Answer 5

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.

There is one in the GoogleSignIn/Resources folder, and the other two are in GPPCore/Resources folder. (click the .bundle)

Answer 6

I am getting the same error with TapJoy Bundle Resources.

TapJoy is older version. So this problem is going to be fixed by either:

1. Update TapJoy SDK
2. Remove the string from Executable file of TapJoy's plist, not the app's plist just like user dstudeba suggested. In my case the String was TapJoyResources I removed that and worked perfect!

Note: that plist was located at TapJoy's framework files. This error is exactly the same as with this Google Signin SDK issue.

Here's what I did in detail: