Bug 17078 - Having the wrong profile for release configuration results in Runtime error System.DllNotFoundException: libc.dylib
Summary: Having the wrong profile for release configuration results in Runtime error S...
Status: RESOLVED FIXED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Other ()
Version: 1.6.19
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Aaron Bockover [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2014-01-06 15:33 UTC by Jon Goldberger [MSFT]
Modified: 2014-08-22 18:15 UTC (History)
2 users (show)

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


Attachments
Test project (31.97 KB, application/zip)
2014-01-06 15:33 UTC, Jon Goldberger [MSFT]
Details


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 Jon Goldberger [MSFT] 2014-01-06 15:33:49 UTC
Created attachment 5767 [details]
Test project

A couple of issues are in the below note case, but the relevant issue is towards the end of the case thread.I am guessing that without the correct profile that the Mono runtime is not included in the app package and thus the error. So the issue here is more one of better error messaging?  
To repro, open the test case and run using a Mac Developer certificate (fails with noted exception) and then run using a Mac Developer Application certificate (builds and runs).
Comment 3 Mohit Kheterpal 2014-08-21 08:36:19 UTC
I have tried to reproduce this issue but I am not able to reproduce it.

I have run the attached project in release mode with correct profile and it run successfully without any error.

I have run the attached project with current beta build of xam.mac i.e. 1.10.0.9-1

Could you please run the attached project with xam.mac 1.10.0.9-1(Beta) if possible ? And let us know if this issue still exist.

Thanks
Comment 4 Jon Goldberger [MSFT] 2014-08-22 18:15:24 UTC
I am not seeing this issue using Xam.Mac version 1.8.1.6

Hence closing this issue.