AppStore Submission - Missing or invalid signature - com.google.GPPSignIn3PResources

Question

I\'m trying to submit an iOS app to AppStore and I\'m having the following error:

ERROR ITMS-9000: \"Missing or invalid signature. The bundle \'com.goog

Answer 1

By removing all Info.plist file form goolepplus.bundle file work for me.

Answer 2

Adding --deep flag didn't help me, so I solved the issue in a simple and elegant way (sarcasm detected). I removed Google+ SDK from Podfile, then downloaded SDK from here and installed it in a old-fashioned way.

Answer 3

Google just released an updated version 1.7.1, which can be downloaded from their website https://developers.google.com/+/mobile/ios/getting-started. Currently it's still not mentioned in their Release Notes though.

If you're using cocoapods you can copy the current 1.7.0 podspec, create a local one and change all the version references in their to 1.7.1 until the new one is merged into the official cocoapods repo.

Answer 4

my solution for Google Plus looked this way

• deleted the 3 bundles from frameworks from my project
• downloaded new Version 1.7.0 (had to upgrade anyway)
• i opened the GooglePlus.bundle and removed 3 files (GPPSignIn3PResources,GPPShareboxSharedResources.bundle,GPPCommonSharedResources.bundle) as all 3 files will give you a warning in itunes
• I added the 3 bundles back to frameworks
• i tested my Google + login in app ... works
• submitted ...

and run into a new issue (arm64 requirement), unrelated to this one :)

I think this should work if you don't need the resource files like login button.

Answer 5

I had the same error when I tried to submit the app with xcode 6.1. Nothing worked and I really tried everything. Then I found a solution on apple developer forums. It worked for me:

• Go into Keychain Access
• Go into Login keychain
• Delete Apple World Wide Developer Relations Certificate Authority
• Go into System keychain
• Delete Apple World Wide Developer Relations Certificate Authority
• Download new WWDR certificate
• Install it in Login keychain (just clicking it did that)

link: https://devforums.apple.com/message/1072465#1072465

Answer 6

This issue appears to have been fixed today by Apple, after being broken for ~24 hours.

Submitting the same app today, with no changes to the .bundle, no longer throws the error.

--deep code signing of the bundle is not required.

(Note that I did not test this with the specific Google bundle that the question references. The Resources Bundle that our app uses, though, now works correctly and no longer throws the error.)