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.
# Steps to reproduce
run on simulator
# Expected behavior
# Actual behavior
# Supplemental info (logs, images, videos)
# Test environment (full version information)
Created attachment 25373 [details]
Can you please provide the full information of your environment to be able to pinpoint a specific version and a small test case of the crash. It does look to be network related which was changed a few versions ago and I would need this information to know the code you are running.
WE do know there are some changes in ssh but I would need to get a code sample to ensure that is the issue.
Can't seem to reproduce it anymore. Have no idea what fixed it. Perhaps all the restarts/reboots, recreation of provisioning profiles, etc. did the trick.
Very frustrating that this seems to be a recurring theme for each Xamarin upgrade.