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 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.
I discovered another bug in the iOS designer in VS.
declaring an event handler in one control is replicated across all the controls in the view controller
steps to reproduce:
1. drag few controls (buttons) into the view controller.
2. From properties, click on the Events tab and declare an event.
3. click on a different control and notice that the same event is also present in that control (or any other ones in the view controller).
when an event handler is added via the designer, it gets replicated across all the controls in the view controller.
event handlers should be control's specific. each control (view) needs to have its own set of control. similar to how xcode declares Outlets and Actions.
if you want to hook up the same handle to multiple controls of the same type, it needs to be done explicitly.
Xamarin iOS 220.127.116.11
Xamarin VS 18.104.22.168
This should've been fixed as part of https://github.com/xamarin/md-addins/commit/414dc49d7964c7a66c793da718785b7b9c329d96. The issue was the property panel was not updating correctly so it did not accurately reflect the actions associated with the selected control. It should be fixed as part of the next cycle8 release.
*** Bug 42736 has been marked as a duplicate of this bug. ***