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 24320 [details]
Shows empty document outline
When I open a .xib and also the Document Outline the last shows no content at all.
Microsoft Visual Studio Professional 2017
Microsoft .NET Framework
Xamarin 126.96.36.1995 (306f76a)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android SDK 188.8.131.52 (0cd0214)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 10.12.0.14 (bf350ba)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
Created attachment 24321 [details]
Shows empty doment outline
Sorry, added wrong attachement. Here's the correct one.
*** Bug 59027 has been marked as a duplicate of this bug. ***
It might be worth noting that if you drag a UIViewController onto the XIB canvas, the UIViewController does show in the document outline. So it would seem that iOS Designer is not adding UIViews that are not in a UIViewController to the document outline.
Note: If I change to another tab and come back to the xib tab I can see the document outline again.
Fixed in https://github.com/mono/xwt/pull/722
The patch had to be reverted as it triggered crashes in WPF. We'll have to solve this another way. This sounds like it requires intimate knowledge of the XWT layout engine so perhaps this would be better off assigned to someone who understands it?
I attached screenshots and the stacktrace to the original PR and reverted the commit from master already.
As an alternative take on the original patch I tried to move the UpdateLayout call to another place, but it also does not work as expected. If you drag one viewcontroller then it doesn't show up in the treeview. If you drag a second one then the first viewcontroller will show up in the treeview. If you drag a third one then you'll see the first two ViewControllers in the panel.
I believe the crash we're experiencing is caused by this re-entrancy:
We should not be re-entrantly calling ItemContainerGenerator like this. We're adjusting the child collection while we're adjusting the child collection.
Hey Alan, as far as I know you've reverted the original commit that caused the issue. What should we do with this bug?
I haven't reverted the original patch which seems to have introduced the issue. I was hoping someone more familiar with the code could make a better attempt to fix the issue with the additional information we have now.
If they can't then reverting the commit which broke the panel seems like the way forward, but we'd have to test it thoroughly before we commit it to make sure nothing breaks.
Just in case that ends up being what we do - can you revert that original commit locally and give it a thorough check to make sure it doesn't cause other unexpected crashes?
Fixed in version 184.108.40.2064 (d15-5)
Author: Alexander Sorokin
Commit: 2975e87e04cb32e0801a70a2e47090a740d83db3 (mono/xwt)
Included in Commit: 023734e3dfb9914ee6459ee15aea131351c2f42d (xamarin/XamarinVS)
We reverted the original change which appears to remove the re-entrancy we saw in comment 8