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.
Created attachment 16325 [details]
when I add an UITableView or I try to change it for example adding a constraint on the Xib designet, it show me this error:
System.NullReferenceException: Object reference not set to an instance of an object.
at MonoTouch.Design.Client.Windows.NativePropertyTable.<>c__DisplayClass39_0.<RefreshPropertyChooseEditor>b__1(PropertyChooseEntry t)
(see the attachment for the complete stacktrace)
If I undo the last edit (as designer suggest me) the tableview are removed and the error disappeare but instead if I close the view and I reaopen it, all work correctly utill I try to edit or move the tableview. Plus if i click on UITableView before moving it and click on property tab, it doesn't work and shown the last element selected.
Please help because I can't edit any xib that use UITableView!
Already fixed in master:
Oh, no. This is different to the fix i mentioned above.
This should've been fixed as part of https://github.com/xamarin/md-addins/commit/8fa0720624eda595ef77bd1b2749ca787790188e
*** This bug has been marked as a duplicate of bug 41907 ***
I am still getting the NRE with XVS 184.108.40.206 (cycle7-sr1/e8360de)
But, this is working in XVS 220.127.116.1101 (master/7333d13). So, I am guessing that the fix just hasn't made it into cycle7-sr1 yet.
We're unlikely to be able to backport a fix easily if that patch didn't fix it. Is this important enough to burn potentially several days to figure out what needs backporting?
as per comment 5, This issue is working fine with master build, and we are unable to check this issue with xvs-win-cycle8 build as builds are failing in this lane.