Sebastien Pouliot

> We solved the watchdog problem for the simulator, but never for device. @rolfbjarne damn, I preferred the confort of my memories ;-) I guess I mixed up the sim...

This is a recurring issue with the .net iOS SDK (and the previous Xamarin.iOS SDK). It might be a good idea to run something like `/usr/local/share/dotnet/packs/Microsoft.iOS.Sdk/16.4.7067/tools/bin/mlaunch --listsim=X` after the validation/installation...

> I think this problem will be somewhat related to: #9132 c.c. @mandel-macaque > I don't think it's possible to create one because I'd need to roll it out to...

re-opening issue so this gets reviewed in 30 days (if not earlier) thanks!

> But still got the same exception from production (AppStore) which afterwards ended up with a crash: @mandel-macaque ^ > Is there a way I can retrieve the Xamarin.iOS version...

> to build binary logs on VS for Mac: Not sure you can do them from VS for Mac. You normally want to be able to read build logs if...

A tricky part is that dotnet msbuild files are re-using / sharing code with _legacy_ ones. We do not want (and must take care) to change the existing behaviour. Also...

I was about to suggest `fixed` instead of allocating (and free'ing) two `GGHandle` but @rolfbjarne suggestion is even simpler :)

It's not automatic but with #103 you can right click on the assembly and select `Reload Assembly`, which is simpler/faster than before. About automatic I'm not sure we always want...

There are more and more privacy issues around Chrome. Maybe we should check for Edge and/or Chromium too ? and warn if none of them (3) are present ? [1]...