Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
The app bundle appears to be based on the name of the project. If I have a project named MyApp.Mac, but my output->Assembly Name is "My App" Xamarin studio will build, but can execute it. It outputs in the bin/Debug directory MyAppMac.app.
So, I'll have
If I were to rename that project to MyApp.Mac2 I'd get:
Long and short of it is that at some point the output-assembly name in the project settings is ignored when generating the app bundle.
This is using Xamarin.Mac 188.8.131.52 and on unified. I don't believe this is an issue with classic.
This is fixed with maccore / f86ff68d1f515d670795858c6195458a67a16794.
I have a request out for merging this into 1.12.