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.
This is a public version of bug 27995 for tracking purposes, but I am also making it more general as bug 27995 is filed against Xamarin for Visual Studio, but I have confirmed the issue in Xamarin Studio as well.
Basically if the companion app project references a PCL then the Plugins folder with the Watch extension does not get placed in the companion app bundle. Then when trying to deploy the Watch app, the deployment hangs with the "Waiting for debugger to connect" in the status bar and the Watch app won't launch.
I have been unable to reproduce this with a newly created project, but I was able to reproduce this in Xamarin Studio with a customer's project in Xamarin Studio. (See private comment below)
*** This bug has been marked as a duplicate of bug 27995 ***
@Jeff it sounds like the "watchapp" condition does not work under that scenario
What's the status on this? I can't access 27995, any advice on how I can move forward?
Will it work if I create a new PCL project and migrate all my code over?
I recommend removing the "Microsoft.Pcl.Build" NuGet and things will work.
I found the root cause for this. The given targets file is redefining GetTargetPath, which Xamarin.iOS also redefines and is key to properly build and bundle stuff across app/extension/watchapp.
The "simple" fix is to move the Xamarin.iOS targets to the bottom of the csproj. We need to implement an explicit fix in the IDEs to do this automatically on project load and after nuget package install (since NuGet in VS modifies this automatically).
*** Bug 29007 has been marked as a duplicate of this bug. ***
Microsoft.Bcl.Build referenced from an app project breaks the build for Today Widgets also. The Today Widget extension is not bundled with the app if the iOS app project references Microsoft.Bcl.Build and a PCL.
this is fixed now
*** Bug 29912 has been marked as a duplicate of this bug. ***
I am using the Beta channel with the "fix" for it, but I am still getting the exact same issue as before.
*** Bug 26605 has been marked as a duplicate of this bug. ***
*** Bug 30383 has been marked as a duplicate of this bug. ***
I still see this problem with the latest stable builds:
* Xamarin Studio Version 5.9.5 (build 10)
* Xamarin.iOS Version: 184.108.40.206 (Enterprise Edition)
Removing BCL.Build fixes it still - is it possible that there is a regression?
I see this problem too.
I'm using XS Stable 5.9.5 build 10, with Xamarin Forms 220.127.116.1192.
I am not able to remove Microsoft.Bcl.Build because other packages in my iOS project depend on it.
This is still occur on:
=== Xamarin Studio ===
Version 5.9.7 (build 9)
Installation UUID: fe69ddf8-5edc-42a6-ac7a-fe710eb02c0e
Mono 4.0.4 ((detached/cb6d6b2)
GTK+ 2.24.23 (Raleigh theme)
Package version: 400040002
=== Xamarin.Android ===
Version: 18.104.22.168 (Business Edition)
Android SDK: /Users/codybeyer/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
4.0.3 (API level 15)
4.4 (API level 19)
5.0 (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
=== Xamarin Android Player ===
Version: Unknown version
Location: /Applications/Xamarin Android Player.app
=== Apple Developer Tools ===
Xcode 7.0 (8227)
=== Xamarin.iOS ===
Version: 22.214.171.124 (Business Edition)
Build date: 2015-09-18 23:22:05-0400
=== Xamarin.Mac ===
Version: 126.96.36.199 (Business Edition)
=== Build Information ===
Release ID: 509070009
Git revision: 31fa64709030b3edb971237780a452a4c69943c4
Build date: 2015-09-17 11:44:37-04
Xamarin addins: b105d33d8cd72911ff2cf3ee0b7715d37e5f19a6
=== Operating System ===
Mac OS X 10.11.0
Darwin Codys-MacBook-Pro.local 15.0.0 Darwin Kernel Version 15.0.0
Wed Aug 26 16:57:32 PDT 2015
Using the following steps:
1. Added a new Share extension project to my solution.
2. Added a reference to the Share extension project in the main app project
3. Changed the CFBundleIdentifier to match the main app identifier + the extension name
4. Run the project in the simulator
5. Open up Safari and click the Share icon.
6. Select more.
7. Nothing happens I don’t see my app in the list
I have now filed a fresh bug report that includes a minimal test case for this problem to promote a clean and accurate bug fix.
I will mark this bug as a duplicate of that new bug for bookkeeping.
*** This bug has been marked as a duplicate of bug 35323 ***