Bug 24545 - Unified launcher does not launch when assembly name != bundle name
Summary: Unified launcher does not launch when assembly name != bundle name
Status: RESOLVED FIXED
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: Other ()
Version: 1.10.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Chris Hamons
URL:
Depends on:
Blocks:
 
Reported: 2014-11-14 15:46 UTC by Chris Hamons
Modified: 2014-11-26 07:59 UTC (History)
6 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 Chris Hamons 2014-11-14 15:46:21 UTC
- Create a new unified project
- Change the assembly name of the exe to FooBar (assuming your project isn't named FooBar.
- Run. Note the failure
- Switch it to match your bundle name.
- Try this in classic and note the lack of an issue.
Comment 1 Udham Singh 2014-11-17 04:47:18 UTC
I have checked this issue with the help of instructions provided in bug description and observed that for Unified project we are getting error "The application has not been built.", while for classic this is working fine. Please refer the screencast : http://www.screencast.com/t/5DP3E1VP

Build Output : https://gist.github.com/Udham1/0d85453804dd768a7e2a
Ide Log : https://gist.github.com/Udham1/add6174c1ce9eaef1015

Environment Info :

=== Xamarin Studio ===

Version 5.5.3 (build 6)
Installation UUID: ce927b2a-2c07-44c5-b186-09cfdafba6dc
Runtime:
	Mono 3.10.0 ((detached/e204655)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000023

=== Apple Developer Tools ===

Xcode 6.1 (6602)
Build 6A1052c

=== Xamarin.Mac ===

Version: 1.10.0.18 (Enterprise Edition)

=== Build Information ===

Release ID: 505030006
Git revision: fbe3e9453daf6a3bb9a9709ed22bec35f7c9056b
Build date: 2014-10-23 13:08:38-04
Xamarin addins: e44add2b39de4dd57c0742bb2e620dfad84c64c6

=== Operating System ===

Mac OS X 10.9.4
Darwin Xamarin76s-Mac-mini.local 13.3.0 Darwin Kernel Version 13.3.0
    Tue Jun  3 21:27:35 PDT 2014
    root:xnu-2422.110.17~1/RELEASE_X86_64 x86_64
Comment 3 Chris Hamons 2014-11-18 15:26:45 UTC
One work around (beyond not using the standard AssemblyName == BundleName (with only ascii and _ characters) is to set the following key in your info.plist:

	<key>MonoBundleExecutable</key>
	<string>$(EXE_NAME).exe</string>

where $(EXE_NAME) is your renamed assembly name. This will break XS debugging however, so it isn't a perfect work around.
Comment 5 Rolf Bjarne Kvinge [MSFT] 2014-11-26 07:59:49 UTC
Fixed.

maccore/master: f86ff68d1f515d670795858c6195458a67a16794
xamcore/master: 5d6b61f8691b983ec15ca5e8a4e568c0dba84f44