Bug 23657 - Build server throws internal exception when listing devices
Summary: Build server throws internal exception when listing devices
Status: RESOLVED DUPLICATE of bug 23353
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 3.7
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-10-06 17:00 UTC by Rogier van der Hee
Modified: 2015-01-05 11:20 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
VS logs (7.13 KB, application/x-zip-compressed)
2014-10-06 17:00 UTC, Rogier van der Hee
Details
server log part (1.84 KB, application/msword)
2014-10-06 17:00 UTC, Rogier van der Hee
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 23353

Description Rogier van der Hee 2014-10-06 17:00:25 UTC
Created attachment 8324 [details]
VS logs

I can’t seem to get Visual Studio 2013 to recognize the connected iDevice on my Macbook Pro. Obviously, I have installed the latest version rebooted / reconnected / restarted the Apple/iPad/BuildServer.

I'm on Xamarin.iOs 8.2.0.193 and build server version 3.7.201.

There is something going wrong in the Device constructor.

If you look in the log, there is an error:
[06-Oct-2014 22:52:11] Error: Command [ListDevices: CommmandUrl=ListDevices] failed.
[06-Oct-2014 22:52:11] Exception: Exception type: System.ArgumentNullException
Argument cannot be null.
Parameter name: version
  at System.Version..ctor (System.String version) [0x00000] in <filename unknown>:0 
  at Mtb.Server.DeviceListener.<GetDevices>m__1 (Xamarin.MacDev.IPhoneDevice d) [0x00000] in <filename unknown>:0 
  at System.Linq.Enumerable+<CreateSelectIterator>c__Iterator10`2[Xamarin.MacDev.IPhoneDevice,Mtb.Server.Device].MoveNext () [0x00000] in <filename unknown>:0 
  at System.Collections.Generic.List`1[Mtb.Server.Device].AddEnumerable (IEnumerable`1 enumerable) [0x00000] in <filename unknown>:0 
  at System.Collections.Generic.List`1[Mtb.Server.Device]..ctor (IEnumerable`1 collection) [0x00000] in <filename unknown>:0 
  at System.Linq.Enumerable.ToList[Device] (IEnumerable`1 source) [0x00000] in <filename unknown>:0 
  at Mtb.Server.DeviceListener.GetDevices () [0x00000] in <filename unknown>:0 
  at Mtb.Server.Commands.ListDevices.GetDevices () [0x00000] in <filename unknown>:0 
  at Mtb.Server.Commands.ListDevices.HandleRequest (ILoggingHelper logger, System.Object commandRequestState) [0x00000] in <filename unknown>:0 
  at Mtb.Server.BaseCommand.OnRequest (System.Net.HttpListenerContext context, System.Object commandRequestState) [0x00000] in <filename unknown>:0 
  at Mtb.Server.Listener.OnRequest (System.Object state) [0x00000] in <filename unknown>:0 
[06-Oct-2014 22:52:11] Request handled in 7.017ms
Comment 1 Rogier van der Hee 2014-10-06 17:00:52 UTC
Created attachment 8325 [details]
server log part
Comment 2 Brendan Zagaeski (Xamarin Team, assistant) 2014-10-08 23:06:34 UTC
Thanks for the report! I've reopened bug 23353 with some additional information. The `ArgumentNullException` from comment 0 and comment 1 is the same error from that bug, so I'll mark this one as a duplicate.

*** This bug has been marked as a duplicate of bug 23353 ***