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 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.
Steps to reproduce:
1. Open or create iOS Single view application.
2. Add WatchOS2 template.
3. Set valid provisioning profile.
4. make sure watch device displaying in dropdown
5. Debug the application on Watch device.
Actual Result: Application deployed on watch device but debugger not connected.
Expected Result: Debugger should connect.
Supplement Info and Environment details:
Application Output: https://gist.github.com/Arpit360/9bcb00ca9bb275d1eaf6505132163176
Watch device version 2.2.1
iPhone 6S version 9.3.2
This is a known issue, and will not be fixed for the upcoming preview.
PR merged (master): https://github.com/xamarin/xamarin-macios/commit/d747998128fcfb643f42c92b015748d8c2583d85
An updated XS is also required for the fix to be complete (md-addins 05b0b4175687df174e5087e22d6c431e5c9f9640).
Some notes about debugging on watchOS device can be found here: https://github.com/xamarin/xamarin-macios/wiki/Debugging-on-watchOS-device
Verified with XS Version 6.2 (build 424) and XI 188.8.131.52
This has been merged to cycle8: https://github.com/xamarin/xamarin-macios/commit/4298ebfdfb5035ff2388681b8b6ee366c4b8c88c
I have checked this Issue with latest Cycle 8 builds(XI 10.0.0.4), I am still getting this Issue (Not connected to debugger).
Environment info and Logs: https://gist.github.com/tajinder360/f387f683a5713b4d616ae2eed4e9dd6a
Application Output: https://gist.github.com/saurabh360/ee2e93d4cb86ab5649bb05b63b4ff42c
Watch Device log: https://gist.github.com/saurabh360/bef2ee09c1bef4b77ea5152e38995018
iOS Device log: https://gist.github.com/saurabh360/d6814c3f3ae4624f1b436aeeb63b16ad
@Saurabh, can you enable verbose mlaunch logging as described here: https://github.com/xamarin/xamarin-macios/wiki/Debugging-on-watchOS-device and attach the Application Output from when it fails?
Created attachment 17394 [details]
verbose using Watch OS UDID
Created attachment 17395 [details]
verbose using UDID of iPhone
Provide logs in above comments#11 and comment#12
@Saurabh, what I need is the output in the Application Output pad from Xamarin Studio.
Application Output: https://gist.github.com/saurabh360/10a300eb07fb307c18219201bff8b3df
@Saurabh, there seems to be something wrong with the network connection between the watch and the mac:
a) Is the IP of the mac correct: 192.168.7.28?
b) Is the phone connected to that same network (using wifi)?
c) Does debugging on the phone work if you enable wifi debugging?
@Rolf,Now I have both watch and iOS device on same network, breakpoint getting hit successfully.
Application Output: https://gist.github.com/saurabh360/afe08e84925dacedff977dd3d1ed1a9e
So now for debugging on watchOS we will have these perquisite: https://github.com/xamarin/xamarin-macios/wiki/Debugging-on-watchOS-device ?
If this is correct behaviour the we can close it
Yes, it will always be required to have all devices/machines on the same network for debugging to work.
As per comment#17 and comment#18 changing the status to verified.