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.
Using 18.104.22.168 - business edition, Mac OS X 10.8.4, X.S. 4.1.7, Xcode 4.6.1
There looks to be a regression error going from the 6.3.x branch to 6.4.x whereby ViewControllers are losing everything and not being recognised as ViewControllers. Typically it is only seen when compiling and a ViewController is not recognised.
When the XIB is then selected and the connections viewed, there are no connections and no ability to add connections. The designer.cs file is empty as well (it appears as a blank file). The only way to get the connections back is to create a new view controller and copy the old design over and relink the connections.
This seems to have been caused by my VirtualProjectPath lookup optimization that was new in 4.1.7 and should be fixed in 4.1.8
Looks like it is currently broken in 4.3.0
Do you have a test case for this?
This bug seems to have cleared the system now. I'll close it.
I just encountered this same in 5.7 (build 661). Some of the details were slightly off. For example the .designer.cs file was not empty. Also in IB the .h file was not empty. However the symptoms were that my UIViewController derived class could not be implicitly assigned to window.RootViewController, and deleting / recreating the ViewController fixed it.