-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Xamarin.iOS app crashes with NotImplementedException #222
Comments
Does it work if you start on cellular data? |
@serkantkaraca let me check, default transport is same, Amqp, as in #223. |
@serkantkaraca this issue is reproduced when switching from Wi-Fi to cellular. No problem if we start with cellular at once. |
Additional similar stack trace (leads to this line in Mono https://github.com/mono/mono/blob/master/mcs/class/System/System.Net.Sockets/SocketAsyncEventArgs.cs#L257)
There is an easier repro now - run app that constantly sends data to event hub using AMQP (iOS simulator is okay) and then disconnect from Wi-Fi on the host. Simulator app will crash after short time with this error. Issue filed in Xamarin Bugzilla by another person https://bugzilla.xamarin.com/show_bug.cgi?id=60772 Similar issue in Websocket4Net kerryjiang/WebSocket4Net#108 |
We decided to put to test version where we have |
Thanks Alex. I am checking out our code base to find out why we hit NotImplemented on Mono. |
Does it fail the same way if you start the app w/o any available network connection? It seems Mono Socket will crash with NotImplementedException if connection attempt fails. |
The issue seems to be here: https://github.com/mono/mono/blob/0bcbe39b148bb498742fc68416f8293ccd350fb6/mcs/class/referencesource/System/net/System/Net/Sockets/_MultipleConnectAsync.cs#L61 Dns.BeginGetHostAddresses doesn't complete async call and handle the exception from DnsCallback. Are you observing NotImplementedException as the unhandled exception causing the crash or as first chance? |
don't have a sample for that since we need to be online to start the app usually, from what I see it would be exactly same scenario
unhandled |
Opened a new issue in Mono repository to track this: mono/mono#6428 |
There is now a fix there, but we need this to get backported to test it. |
Looks like |
The issue is fixed in Mono |
Actual Behavior
Expected Behavior
Versions
See similar error in Ably ably/ably-dotnet#161
The text was updated successfully, but these errors were encountered: