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

44
votes

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.google.GPPSignIn3PResources' at bundle path 'Payload/My_app_name.app/GooglePlus.bundle' is not signed using an Apple submission certificate."

I've submitted this app before I've never had this problem. Does anybody know if there is any recent change?

Update: I could submit the app about 6 hours before having this error. Then, my app was rejected with this message:

This bundle is invalid - New apps and app updates submitted to the App Store must be built with public (GM) versions of Xcode 5.1.1 or higher and iOS 7 SDK. Do not submit apps built with beta software.

After this, couldn't submit anymore.

Update2:

Google has made an announcement about this:

http://googledevelopers.blogspot.com.br/2014/09/an-important-announcement-for-ios.html

A new version was released, solving the problem.

12
iosxcodeapp-storeapp-store-connect
We are seeing the same exact error attempting to resubmit an app that was uploaded without error (same code) yesterday. Also, the App Review team rejected our binary yesterday saying it was built with a non-GM build of Xcode 5.1.1 but it actually wasn't. I'm suspecting something got broken with all the new changes going on the last few days. – Mark Edington
Exactly the same thing here... was rejected for the same reason as you for my code that was submitted successfully today afternoon. – Raphael Petegrosso
In addition to seeing it on GooglePlus.bundle, we are seeing it on com.google.GoogleMaps. – Dean Liu
I just submitted a rejection appeal to iTunes connect and referenced this question here. I would encourage everyone to do this and also click on the "Submit to Apple" button in the Application Uploader when the upload fails. I do think that the roll out of new iOS 8 / Xcode 6 stuff has very likely broken some tooling. – Mark Edington
I am getting same error, is it safe to assume that its an iTunes bug? – Bhumit Mehta

12 Answers

13
votes

Google released the version 1.7.1 of the google plus sdk.

I created a new podspec for the 1.7.1 version as the previous owner is not reachable.

Just add into your Podfile: 

pod 'googleplus-ios-sdk', '~> 1.7.1'
30
votes

Just remove files below and build your app as usual!

  • GooglePlus.bundle/GPPSignIn3PResources
  • GooglePlus.bundle/GPPCommonSharedResources.bundle/GPPCommonSharedResources
  • GooglePlus.bundle/GPPShareboxSharedResources.bundle/GPPShareboxSharedResources
5
votes

Adding the --deep flag to Other Code Signing Flags (OTHER_CODE_SIGN_FLAGS) in the Project (not target) settings seems to fix this.

3
votes

The correct fix is to upgrade to the 1.7.1 version of the Google Plus iOS SDK. It seems to have been specifically released to fix this problem.

If you diff the 1.7.0 and 1.7.1 bundles you will see that no files were added, but three files were deleted : GPPSignIn3PResources, GPPShareboxSharedResources and GPPCommonSharedResources - the three files that the App Store was complaining about.

1
votes

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.

1
votes

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.

1
votes

If --deep doesn't work, then chances are that the bundle is simply resources and does not actually have any executable file. Delete its Info.plist and you'll be good. If there's some reason you actually need Info.plist, at least delete the CFBundleExecutable key.

1
votes

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

1
votes

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.)

0
votes

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.

0
votes

You should also remove info.plist files

GooglePlus.bundle/info.plist

GooglePlus.bundle/GPPCommonSharedResources.bundle/info.plist

GooglePlus.bundle/GPPShareboxSharedResources.bundle/info.plist

0
votes

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