Bug 34332 - ERROR ITMS-90535: Unexpected CFBundleExecutable Key. Google Plus and Play Xamarin Component
Summary: ERROR ITMS-90535: Unexpected CFBundleExecutable Key. Google Plus and Play Xam...
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Israel Soto [MSFT]
Depends on:
Reported: 2015-09-28 09:03 UTC by matt
Modified: 2015-10-21 16:13 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description matt 2015-09-28 09:03:21 UTC
I've been using the Google Plus and Play Xamarin Component in the iOS version of my cross-platform app. I haven't had any trouble uploading it to the store in the past, but after upgrading to Xcode7, I receive the following error when trying to submit my .ipa through Application Loader:

ERROR ITMS-90535: "Unexpected CFBundleExecutable Key. The bundle at 'Payload/Brushfire.iOS.app/GooglePlus.bundle/GPPShareboxSharedResources.bundle' does not contain a bundle executable. If this bundle intentionally does not contain an executable, consider removing the CFBundleExecutable key from its Info.plist and using a CFBundlePackageType of BNDL. If this bundle is part of a third-party framework, consider contacting the developer of the framework for an update to address this issue."
Comment 1 Israel Soto [MSFT] 2015-09-30 16:03:29 UTC

This issue is presented on all Google APIs.

We are working on a version without this Key on the bundle.
Comment 2 Luigi Saggese 2015-10-01 09:36:02 UTC
My binding doesn't have this issue 


Please check it
Comment 3 Israel Soto [MSFT] 2015-10-01 12:32:48 UTC
Hi Luigi!

Thanks for the contribution.

I have reviewed your project and your project has the new bundle that Google is releasing (in a slowly way). The way you can notice this is by opening the Info.plist file that comes within GoogleSignIn/Resources/GoogleSignIn.bundle folder and see that doesn't have the `CFBundleExecutable` key and also has the new `CFBundlePackageType` key.

We are working on the old ones by removing the `CFBundleExecutable` Key.

We hope have the new release of Google APIs without the key by next week.
Comment 4 Craig Kitterman 2015-10-09 00:52:55 UTC
Any progress on this Israel?  Major blocking issue here for getting our iOS 9 suppport into market.  Thanks!
Comment 5 Israel Soto [MSFT] 2015-10-10 16:47:03 UTC

Sorry for taking so long to give a reply.

I share you the link to the dll with the fix:


This version is the same as the component store but without the CFBundleExecutable Key, is not the latest version released by Google.

Just one note, this component will be deprecated soon because we are going to split the component into two (Google.Plus and Google.PlayGames). But, don't worry, we were working with the latest version of Google APIs, that's the reason we took too long to give a reply. I share you the dlls that will be available on the store soon:

Google Plus: https://www.dropbox.com/s/p8y46ef7tx1ue6o/Google.Plus.zip?dl=0
Google Play Games: https://www.dropbox.com/s/aptguhr2kvmsbsf/Google.PlayGames.zip?dl=0

These two last links contains the latest version that Google released it.

Feel free to play with these versions and, please, let me know if the error goes away.
Comment 6 matt 2015-10-12 09:20:30 UTC
Hi Israel, 

Thanks for the update. Is there any way we can get a more concrete timeline than "soon" for the new components? I'd like to use the official component instead of the dll so that it's in the infrastructure of Xamarin Studio and gets updated automatically and the like.
Comment 7 Shaun 2015-10-12 09:38:59 UTC
Hi there Isreal,

I am experiencing the same errors.  I am using the google nuget API's reference from the following Xamarin article.... https://forums.xamarin.com/discussion/comment/146986

The fixed dll's look like they only apply to the actual Xamarin component.  I am using these updated dll's to help get around the component opening a page in the browser rather than within the app on the device.  How can I get around these errors?  Are these dll's being updated as well?  Currently I am unable to deploy to the App Store.

Thanks for any help you can provide.

Comment 8 matt 2015-10-16 12:34:08 UTC

Any timeline on this? We're currently using the dll, but we really need to use the Component instead.
Comment 9 Israel Soto [MSFT] 2015-10-21 16:13:26 UTC
Google Plus and Play Games Services for iOS issue fixed on version:



Sorry for taking so long to give a reply.

The version with the fix is already available on Components Store:


If you have any issue with the component, let me know.

Happy coding!
Israel Soto.