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.
Created attachment 15974 [details]
Logs and version information
Customer is experiencing time-outs when connected to Mac agent.
= Steps to replicate
Connect to Mac agent from Visual Studio
= Expected results
Mac should stay connected while in use
= Actual results
Mac disconnects on occasion.
Possible relevant information in logs:
Xamarin.Messaging.VisualStudio.MessagingService Error: 0 : [2016-05-05 04:32:06.7116] An error occurred on the underlying client while executing an operation. Details: The operation has timed out.
Xamarin.Messaging.Client.MessagingClient Error: 0 : [2016-05-05 04:32:06.7306] An error occured on client vs7244fatma while executing a post for topic xma/ping/Broker403214
Xamarin.Messaging.Exceptions.MessagingException: There was an error while trying to subscribe to response topic xma/ping/Broker403214 ---> System.Net.Mqtt.Client.ClientException: A timeout occured while waiting for the subscribe confirmation of client for topic vs7244fatma/+/xma/ping/Broker403214 ---> System.TimeoutException: The operation has timed out.
Xamarin - 18.104.22.168-cycle6-c6sr3+0dd817c
(Full information requested but not yet provided
=== Xamarin Studio Enterprise ===
Version 5.10.3 (build 51)
Installation UUID: eb716c73-19a6-42da-8386-d057991c82ab Runtime:
Mono 4.2.3 (explicit/832de4b)
GTK+ 2.24.23 (Raleigh theme)
Package version: 402030004 === Xamarin.Profiler ===
=== Apple Developer Tools === Xcode 7.3 (10183.3)
=== Xamarin.iOS ===
Version: 22.214.171.124 (Visual Studio Enterprise Trial) Hash: 5f11db8
Build date: 2016-03-25 21:26:55-0400
=== Xamarin.Android ===
Version: 126.96.36.199 (Visual Studio Enterprise Trial) Android SDK: Not found
=== Xamarin Android Player ===
=== Xamarin.Mac ===
Version: 188.8.131.52 (Visual Studio Enterprise Trial) === Build Information ===
Release ID: 510030051
Git revision: f3c0d982165f785772d125f02668370d929014fb Build date: 2016-03-24 18:51:31-04
Xamarin addins: ee5cfd3ecb6b20de47c1d25efb9a9abc101e8ce7 Build lane: monodevelop-lion-cycle6-c6sr3
=== Operating System ===
Mac OS X 10.11.4
Darwin 15.4.0 Darwin Kernel Version 15.4.0
Fri Feb 26 22:08:05 PST 2016 root:xnu-3248.40.184~3/RELEASE_X86_64 x86_64
Some similar timeout issues have been reported by users to be fixed on Cycle 7 and higher. (See for example, Bug 38695, Comment 1, and the "preliminary customer verifications" in Bug 38695, Comment 5.)
I will mark as NEEDINFO to check if the reporting user on this bug still sees issues with Cycle 7 or higher. Thanks!
Marking as "resolved noresponse" for now since there has been no further update from the user about the behavior after Cycle 7. Cycle 8 – Service Release 0 contains additional changes to several timeout parameters that might also help with symptoms similar to this.
If the original reporting user still sees precisely the original symptom from Comment 0 when using the latest versions, please do reopen this bug report.