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.
In the newest release (see below for version)
How to replicate bug:
1 Set the RightBarButtonItems to a couple buttons (plural)
2 After it renders,
3 Set the RightBarButtonItem to a single item (just one)
Worked in the last version of mono+monotouch
Solution for now is to set RightBarButtonItems(many) with a RightBarButtonItems(one)
Mono 2.10.9 (tarball Tue Mar 20 15:31:37 EDT 2012)
Apple Developer Tools:
Xcode 4.3.1 (1176)
This is a bit vague. I'm not sure I understand the solution (not use many?).
A small, self-contained test case is always best to ensure we'll be seeing the same (or as close as possible) conditions as you are.
If that cannot be provided can you:
* provide the crash report (stack trace);
* specify your build options (or include the full build log from MD);
* tell us if this happens in the simulator, devices (or both) including the version of iOS you are using (simulator and devices).
If you can recall what was the last MonoTouch version you're sure the exact same code was working ?
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?
If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.
Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.