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.
# Steps to reproduce
I'm not sure if this is reproducible, but at the moment I cannot switch between iOS and Android projects in Xamarin Forms reliably (at least in my current project). VS2015 recognizes only one device, so when I switch contexts, I need to close VS and open it again for the new device to be recognized.
- Run your app on Android device
- Switch to iOS context
- iPhone device is not recognized even though Xamarin Mac Agent is connected.
# Expected behavior
# Actual behavior
# Supplemental info (logs, images, videos)
# Test environment (full version information)
VS2015 with Update 3
iOS 9.0+ (iPhone 6)
Android 6 (Samsung S6)
Can you please attach the Xamarin logs?
Being connected to the Mac (to get Mac logs as well) please do the following:
Help - Tools - Zip Logs.
Created attachment 17252 [details]
see VS logs
changing status back to new so the logs can be looked at.
It seems like you wasn't connected to the Mac when got the logs. Can you please get the logs while **connected** to the Mac? We need more details from Mac logs.
Alternatively, in your Mac, you can browse to "~/Library/Logs/Xamarin-4.2" and zip the logs for the given date.
But I would suggest to use the Visual Studio menu option (while connected) as it's quite simpler.
Also, an interesting check would be if you can create a new Xamarin Forms app from scratch on your side, and see if this issue is also present with that "clean" app.
This seems to be resolved in BETA PREVIEW 3: CYCLE 8. When I updated to preview 3, the issue went away.