Bug 54385 - No way to launch/attach to watchOS complication from debugger
Summary: No way to launch/attach to watchOS complication from debugger
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.8 (d15-1)
Hardware: Macintosh Mac OS
: Normal enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Vincent Dondain [MSFT]
Depends on:
Reported: 2017-04-02 04:41 UTC by t9mike
Modified: 2017-05-19 17:28 UTC (History)
7 users (show)

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

Xcode watch app run options (106.21 KB, image/png)
2017-04-02 04:41 UTC, t9mike

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 t9mike 2017-04-02 04:41:19 UTC
Created attachment 21142 [details]
Xcode watch app run options

Xcode supports launching WatchKit complication: setting breakpoints and seeing log output directly in Xcode IDE. I do not see Complication on XS/VS.NET "Run With-Custom Configuration" window.

Need this desperately in Xamarin. I can get by somewhat on simulator by reviewing console logs (still miss breakpoints, however), but on device this is killing me.

I see my complication behaving differently on device than sim regarding WCSession and need eyes on the problem.

=== Xamarin Studio Enterprise ===

Version 6.3 (build 858)
Installation UUID: 2ef48581-52bf-43ad-b554-cca1ec408cf4
	Mono 4.8.0 (mono-4.8.0-branch/9d74414) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 408000524

=== NuGet ===


=== Xamarin.Profiler ===

Version: 1.4.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Xamarin.Android ===

Not Installed

=== Apple Developer Tools ===

Xcode 8.3 (12169)
Build 8E162

=== Xamarin Inspector ===

Version: 1.2.0
Hash: 62c17e6
Branch: d15-1
Build date: Mon, 20 Mar 2017 02:36:23 GMT

=== Xamarin.Mac ===

Xamarin.Mac not installed. Can't find /Library/Frameworks/Xamarin.Mac.framework/Versions/Current/Version.

=== Xamarin.iOS ===

Version: (Visual Studio Enterprise)
Hash: 06b241f
Branch: d15-1
Build date: 2017-03-24 11:21:18-0400

=== Build Information ===

Release ID: 603000858
Git revision: 9b45838d2486d0c26567c7ebf94487e4daedafd6
Build date: 2017-03-23 12:40:43-04
Xamarin addins: e66d8957d0ff8dd7f727a3cc75de56ca235b5f60
Build lane: monodevelop-lion-d15-1

=== Operating System ===

Mac OS X 10.12.4
Darwin MacBook1 16.5.0 Darwin Kernel Version 16.5.0
    Fri Mar  3 16:52:33 PST 2017
    root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
Comment 1 t9mike 2017-04-02 05:30:11 UTC
I suppose I should open another ticket here or to support, but should this help, since either Xcode 8.3 or XS 6.3 upgrade, when I launch Watch App via debugger it deploys -- and runs complication code if complication on watch face, etc. -- but does not launch the actual watch app. I get the following error:

warning HE0031: Failed to mount developer tools on 'Mike's Phone'.
warning HE0031: Failed to mount developer tools on 'Michael's Apple Watch'.
warning HE0031: Failed to mount developer tools on 'Mike's Phone'.
warning HE0031: Failed to mount developer tools on 'Michael's Apple Watch'.
error MT1007: Failed to launch the application '/Users/mmuegel/Mike/Git/Main2/Projects/SundialWatchApp/App/PhoneApp/bin/iPhone/Debug/device-builds/iphone8.2-10.3/SundialPhoneApp.app/Watch/SundialWatchApp.app' on the device 'Mike's Phone': Object reference not set to an instance of an object. You can still launch the application manually by tapping on it.
Comment 2 t9mike 2017-04-02 05:34:00 UTC
P.S. I want to debug complication running w/out watch app being launched. That is the scenario I am debugging
Comment 3 t9mike 2017-04-05 16:08:12 UTC
Is there a command line way to send compiled watch extension to watchOS device and attach to console as a work around? Basically emulate Xcode feature but no GUI support. Thanks.
Comment 4 Jeffrey Stedfast 2017-04-07 16:16:14 UTC
Those errors look like they are coming from the mlaunch command.
Comment 5 Vincent Dondain [MSFT] 2017-04-07 19:41:51 UTC
I'm looking into this
Comment 6 Rolf Bjarne Kvinge [MSFT] 2017-04-10 14:57:03 UTC
@Mike, can you try updating to the stable channel and see if that fixes your problem?

I believe your version of Xamarin.iOS:

> Version: (Visual Studio Enterprise)

does not have support for Xcode 8.3
Comment 7 Sebastien Pouliot 2017-04-10 16:46:51 UTC
XI is needed to support Xcode 8.3

@t9mike can you please try again with the latest stable and let us know your results ? thanks!
Comment 8 Vincent Dondain [MSFT] 2017-04-11 22:27:36 UTC

I can confirm that debugging is working from Xamarin Studio.

Tried with very recent versions of the products: https://gist.github.com/VincentDondain/845252dd3961d371fd09b496a199da3f

So indeed, updating should solve your issues.

However about: "I do not see Complication on XS/VS.NET "Run With-Custom Configuration" window."

This is an actual problem and I filed 2 issues to cover this:




You will still have to enable the complication manually even when we'll have the "complication mode" but the experience should be a bit nicer.
Comment 9 Vincent Dondain [MSFT] 2017-05-19 17:28:36 UTC
Let us close this bug since the required work for the IDE is tracked in the 2 bugs linked above.

As I said debugging is working from Visual Studio for Mac and updating your Xamarin.iOS to a version that supports Xcode 8.3 should solve the MT1007 error.