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.
We need to patch Clide so that UIThread.BeginInvoke always does an asynchronous call.
The code in ShellPackage.cs for Activation relies on being able to relinquish the UI thread and exceute code on the next iteration of the main loop. If we cannot reliably use BeginInvoke to be asynchronous then the we will have to review the codebase and port away from Clide.UIThread for places where we rely on BeginInvoke being asynchronous.
Fixed in Clide upstream
I have checked this issue with following builds:
Xamarin for VS 1.12.247
Application is taking approximate 1-2 minutes to launch on iOS Simulator. This is mtvbserver log: https://gist.github.com/saurabh360/1d7f1daf8cd10c5ec16e
Please ignore my comment#2 I was verifying Issue Bug 15976 and this comment is for that issue.