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.
Currently you cannot create unified Xamarin.Mac apps in 64-bit that target the mobile profile (which is currently the only supported way of creating 64-bit apps I believe?). This does not happen when targeting the full net45 profile.
To reproduce, create a new Xamarin.Mac unified application, then add the following line to AppDelegate.DidFinishLaunching:
mainWindowController.Window.WillClose += (sender, e) => Console.WriteLine("Woo");
Run the program and try resizing the form - it disappears. From my testing, this is because the WillResize delegate method gets called, but the return value is not properly returned.
I've attached a full sample as well.
Created attachment 10415 [details]
Sample to reproduce the issue
I have checked this issue and with the help of attached project I am able to reproduce the reported behavior.
IDE Log : https://gist.github.com/Udham1/8d61691c52e1f0e1ec41
=== Xamarin Studio ===
Version 5.8.1 (build 8)
Installation UUID: ce927b2a-2c07-44c5-b186-09cfdafba6dc
Mono 3.12.1 ((detached/b63df7d)
GTK+ 2.24.23 (Raleigh theme)
Package version: 312010002
=== Apple Developer Tools ===
Xcode 6.2 (6776)
=== Xamarin.iOS ===
Version: 188.8.131.52 (Business Edition)
Build date: 2015-03-12 15:35:49-0400
=== Xamarin.Android ===
Version: 184.108.40.206 (Business Edition)
Android SDK: /Users/xamarin76/Desktop/android-sdk-macosx
Supported Android versions:
1.6 (API level 4)
2.1 (API level 7)
2.2 (API level 8)
2.3 (API level 10)
3.1 (API level 12)
4.0 (API level 14)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)
=== Xamarin Android Player ===
Version: Unknown version
Location: /Applications/Xamarin Android Player.app
=== Xamarin.Mac ===
Version: 220.127.116.11 (Business Edition)
=== Build Information ===
Release ID: 508010008
Git revision: f8e52bf493869b6a320a95400553dc9ea8b7ef22
Build date: 2015-03-13 16:16:49-04
Xamarin addins: 84d611cc17567a68daad719327e90af06d2ae327
=== Operating System ===
Mac OS X 10.9.5
Darwin Xamarin76s-Mac-mini.local 13.4.0 Darwin Kernel Version 13.4.0
Sun Aug 17 19:50:11 PDT 2014
Curtis - We _just_ actually found this ourselves earlier this week. There was s subtle registar marshaling bug that is only hit on 64-bit, and only in some cases (as you found).
Try this package:
That has a fix that fixes it for me. I'm going to post a link on the forum for this fix. It will be fixed in XM 2.0, which should be hitting alpha within a week or two.