Bug 42915 - Mono.framework error --> Unsealed contents present in the root directory of an embedded framework In subcomponent: /ABC.app/Contents/Frameworks/Mono.framework".
Summary: Mono.framework error --> Unsealed contents present in the root directory of a...
Status: RESOLVED ANSWERED
Alias: None
Product: Installers
Classification: Mono
Component: General ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Kumpera
URL:
Depends on:
Blocks:
 
Reported: 2016-07-29 10:18 UTC by Sanketh Bhat
Modified: 2016-07-29 15:35 UTC (History)
2 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 GitHub or Developer Community 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 ANSWERED

Description Sanketh Bhat 2016-07-29 10:18:37 UTC
- We use Mono.framework being embedded into your "ABC.app".
- We package "ABC.app" and sign it with Apple certificate. While signing the ABC.app  using  the command [codesign -f -s "Intuit" --deep "ABC.app"]
- We are getting the following error "ABC.app: unsealed contents present in the root directory of an embedded framework In subcomponent: /ABC.app/Contents/Frameworks/Mono.framework".

Please note this has become an blocker for us to launch the application into production, it would be great if Xamarin can look into this to provide some resolution.

Also when we try code signing just the framework, it builds fine "codesign --verbose --force --sign "$IDENTITY" "$LOCATION/Mono.framework/Versions/Current"", but when we try to sign the whole application we are running into above issue.

Please let me know if more information is required.

Mono framework version: 2.10.9

Thanks,
Sanketh Bhat
Intuit Inc
Bangalore
sanketh.bhat@gmail.com
+91-9448414774
Comment 1 Chris Hamons 2016-07-29 15:34:51 UTC
Sanketh,

It sounds like you are building an application, likely not using Xamarin.Mac Unified, and having trouble code signing. Given the description you posted, I don't believe this fits into the criteria of a bug however. Mono is likely not doing anything wrong, your bundle structure or signing command is likely wrong at first glance.

Because of this, I'm going to close this bug. If you have a simple question on code signing you can post it on stack overflow, or if you believe your question is more in depth (requires a code sample for example) feel free to post on the Xamarin.Mac forums (http://forums.xamarin.com/categories/mac).

As a side note, the following documentation may be useful to go over -https://developer.apple.com/library/mac/technotes/tn2206/_index.html

This might give you more information:

$ codesign --verify --deep --verbose=2 Foo.app

And this section on nested code might be useful as well:

https://developer.apple.com/library/mac/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG201
Comment 2 Chris Hamons 2016-07-29 15:35:16 UTC
And just to note, I'm the Xamarin.Mac lead and I often swing by the forums. o/