Bug 26069 - After renaming with v0.2.5, unable to find device with the name: "old name"
Summary: After renaming with v0.2.5, unable to find device with the name: "old name"
Alias: None
Product: Xamarin Android Player
Classification: Xamarin
Component: Device Manager ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-01-15 11:04 UTC by Nate Cook
Modified: 2015-02-24 13:23 UTC (History)
3 users (show)

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

XAP log files as requested (755.30 KB, application/zip)
2015-01-29 15:33 UTC, Nate Cook

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 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.

Related Links:

Description Nate Cook 2015-01-15 11:04:33 UTC
Now with v0.2.5 rename works, but the virtual device list in Xamarin Studio doesn't refresh (even after rebooting my machine). When I try to start the device that I renamed, I get "Unable to find device with the name: old name."
Comment 1 Nate Cook 2015-01-15 11:20:34 UTC
After renaming the device back AND subsequently performing a factory reset on the device, the device boots up again. (Before performing the factory reset, I got an error message saying "device improperly configured", or something to that effect.)
Comment 2 Nate Cook 2015-01-29 15:33:23 UTC
Created attachment 9568 [details]
XAP log files as requested
Comment 3 Nate Cook 2015-01-29 15:34:50 UTC
My OS info as requested: OSX Yosemite 10.10.1 (14B25)

Xamarin studio version is 5.7 build 661

I do NOT log on to a company-managed domain
Comment 4 Will Schaller 2015-02-05 10:44:21 UTC
This is related to an issue with the configuration files for devices with 0.2.5. There is a fix for this in Xamarin Studio version 5.7.1, which is in the Beta channel at the moment and will be in stable very soon. Updating to that should fix this, alternatively you should be able to launch the renamed machines directly from the XAP device manager without issue.
Comment 5 Nate Cook 2015-02-18 12:45:40 UTC
I can confirm that 5.7.1 now recognizes the renamed device, so you can probably close this bug. One question before you do though: After renaming I still need to perform a factory reset on the virtual device before it will boot up. Is that to be expected?
Comment 6 Will Schaller 2015-02-24 13:22:20 UTC
Hi Nate, that shouldn't be required, no, but I've been able to reproduce it so will open another bug report for that bug. Thanks for the reports!
Comment 7 Nate Cook 2015-02-24 13:23:33 UTC
Thank you for looking into it. Would you mind posting the link to that other bug once you've created it?