Bug 30707 - Watchkit Extension app in existing xamrarin iOS project
Summary: Watchkit Extension app in existing xamrarin iOS project
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: XI 8.9.x (iOS 8.3)
Hardware: PC Mac OS
: Normal normal
Target Milestone: Untriaged
Assignee: Bugzilla
: 30706 ()
Depends on:
Reported: 2015-06-03 05:56 UTC by Brij
Modified: 2016-06-09 00:21 UTC (History)
4 users (show)

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

Here It Got stuck (136.41 KB, image/jpeg)
2015-06-03 05:58 UTC, Brij

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 Brij 2015-06-03 05:56:12 UTC
When I adding watch kit extension app in existing iOS app its not working.

It got stuck on "waiting debugger to connect" every time without any log..

I tried in 3 apps.

Refer attached screen shot.
Comment 1 Brij 2015-06-03 05:58:34 UTC
Created attachment 11446 [details]
Here It Got stuck
Comment 2 Sebastien Pouliot 2015-06-03 08:19:49 UTC
*** Bug 30706 has been marked as a duplicate of this bug. ***
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-06-03 12:56:47 UTC
Can you try our WatchKitCatalog sample [1] and see if that works for you?

Comment 4 Sebastien Pouliot 2016-06-09 00:21:53 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks!