Bug 34146 - Failed deploying Xamarin.iOS-app using HockeyApp component 3.7.1.0 after iOS9 release
Summary: Failed deploying Xamarin.iOS-app using HockeyApp component 3.7.1.0 after iOS9...
Status: RESOLVED FIXED
Alias: None
Product: Components
Classification: Xamarin
Component: Xamarin Components ()
Version: Production (addons.xamarin.com)
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bill Holmes
URL:
Depends on:
Blocks:
 
Reported: 2015-09-22 02:46 UTC by Markus Millfjord
Modified: 2015-10-09 19:11 UTC (History)
7 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Markus Millfjord 2015-09-22 02:46:56 UTC
I'm using HockeyApp component for crash-detection and tracing, and it has ben working well with the 3.7.1.0 official release using Xamarin Studio. But, after upgrading our app to iOS9, we suddenly fail when uploading the file to AppStore;

ERROR ITMS-90535: "Unexpected CFBundleExecutable Key. The bundle at 'Payload/myapp.app/HockeySDKResources.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."

And indeed, in the obj/iPhone/Release folder of my app in the Xamarin folder, there's a HockeySDKResources.bundle file that contain an Info.plist file which *does* have the key "CFBundleExecutable" defined. 

So -- here I am, contacting "the developer of the framework for an update" ;)
Comment 1 Sebastien Pouliot 2015-09-22 08:34:43 UTC
We are not the developer of the Hockey SDK nor do we ship the HockeySDKResources.bundle  with our own SDK. 

OTOH it is shipped in our components store so I'll transfer the bug to them

[1] http://support.hockeyapp.net/discussions/problems/46191-failed-deploying-xamarinios-app-using-hockeyapp-component-3710-after-ios9-release
Comment 2 Markus Millfjord 2015-09-22 08:53:27 UTC
;)

As you can see, if you read the forum @ HockeyApp, which you linked me to, it's the original supper-request that I created myself, that ended up in HockeyApp-team pointing to Xamarin team to resolve...

We're going in circles! :)

Please clarify/let me know where I should be requesting support on this issue.
Comment 3 Sebastien Pouliot 2015-09-22 09:16:01 UTC
> We're going in circles! :)

No, we are not :-)

I saw that the request was coming from you (because I read it ;-) and I added the link as a reference, for the component team (so they don't have to google why again), to which I transferred the bug ownership. 

> OTOH it is shipped in our components store so I'll transfer the bug to them

That's because fixing this issue can only be done (and published) by the component team updating the version of Hockey they are shipping (on the component store).

IOW the bug was misfiled* as there's nothing the XI team can do to fix this (we do not ship it, so we can't update it).

* that's no big deal, you are definitively not required to know our team's structure :-) but we do need to re-assign such bugs to the right team (or they won't be resolved).
Comment 4 Markus Millfjord 2015-09-22 09:18:13 UTC
Ahhh!
Thank you of the explanation ;)

Looking forward to feedback from the component team then!
Best,
/Markus
Comment 5 Kshitij Limaye 2015-09-23 20:31:26 UTC
Any updates on this? I am using the following. I have a critical update that has to go out. Please advise asap.

=== Xamarin Studio ===

Version 5.9.7 (build 9)
Installation UUID: e27dc9cc-76c5-4ac7-950e-9a7e6d60d34f
Runtime:
	Mono 4.0.4 ((detached/cb6d6b2)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400040002

=== Apple Developer Tools ===

Xcode 7.0 (8208.9)
Build 7A192o

=== Xamarin.iOS ===

Version: 9.0.1.18 (Business Edition)
Hash: d230615
Branch: master
Build date: 2015-09-16 17:04:13-0400

=== Operating System ===

Mac OS X 10.10.5
Darwin Kernel Version 14.5.0
    Wed Jul 29 02:26:53 PDT 2015
    root:xnu-2782.40.9~1/RELEASE_X86_64 x86_64
Comment 6 Jens 2015-09-24 14:48:33 UTC
I am also struggling... this is a blocker for me :-/
Comment 7 Jens 2015-09-25 09:03:58 UTC
as additional info: 
according to the link above the problem is already fixed in the official 3.7.2 package, so xamarin has "only" to update the package with the latest release, so it shouldn't take too long :)
Comment 8 Jon Dick 2015-09-28 09:35:33 UTC
v3.8.2 of HockeyApp for Xamarin.iOS has been released to the component store.
Comment 9 Jens 2015-09-28 10:45:17 UTC
Thanks for fixing this fast :)

I could upload a version using the updated component to the app store without error message (I got one before), so it seems to work :)
Comment 10 Kent Green [MSFT] 2015-10-09 19:11:49 UTC
Customer hitting an issue that looks similar to this one (though I haven't confirmed yet) in v3.8.2.1: https://kb.xamarin.com/agent/case/221358

Requesting info to try to determine if the issue is the same / wasn't fixed somehow, or if a new issue has cropped up.