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.
When using a container view with an embed segue the runtime crashes with "Could not instantiate class named UIStoryboardEmbedSegueTemplate". Looking through the MonoTouch library there are no references to this class which implies missing support.
This renders container views useless within storyboards.
1. Create a new storyboard application
2. Add a Container View
3. If it's not auto-created, add a new view controller with a segue from the Container View to the new controller.
4. Compile and run
The UIStoryboardEmbedSegueTemplate class is an internal class that is not to be found in the public headers, that means that we probably won't be creating a bindings for it. On the other hand, I have found that such an error is also common in objc projects and is probably an issue with the objc runtime.
I have been able to find headers in other projects that do show the class BUT those are not apple headers, for example:
And an example of the same error in an objc project can be found here:
I tried to reproduce your issue with the latests Xamarin release and I have not been able to do so. Could you provide an example project, just to make sure that I am addressing the bug as expected?
We have not received the requested information. If you are still
experiencing this issue please provide all the requested information
and re-open the bug report. Thanks!