Bug 28082 - Disable watchkit extension for universal apps launched from iPad
Summary: Disable watchkit extension for universal apps launched from iPad
Status: RESOLVED DUPLICATE of bug 28078
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: master
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Vincent Dondain [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2015-03-16 16:33 UTC by Cody Beyer (MSFT)
Modified: 2015-03-16 21:04 UTC (History)
2 users (show)

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

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:
Status:
RESOLVED DUPLICATE of bug 28078

Description Cody Beyer (MSFT) 2015-03-16 16:33:00 UTC
### Description

When using adding a watchkit extension to a universal project, the watchkit extension is included when deploying to iPad

### Steps to Reproduce

1. Create Universal App
2. Add WatchKit Extension
3. Deploy to PHYSICAL iPad device

### Expected Results

The WatchKit extensions should not be included with the incompatible OS/Device

### Actual Results

The WatchKit extension attempts to load with the following error:  This app contains an app extension that specifies an extension point identifer that is not supported on this version of iOS for the value of the NSExtensionPointIdentifier key in its Info.plist.

### Version

=== Xamarin Studio ===

Version 5.8 (build 463)
Installation UUID: fe050df7-44bb-4337-87ab-a8e27643bb7d
Runtime:
	Mono 3.12.1 ((detached/7a2a192)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312010001

=== Apple Developer Tools ===

Xcode 6.2 (6776)
Build 6C131e

=== Xamarin.iOS ===

Version: 8.8.1.9 (Business Edition)
Hash: 7e1f69e
Branch: 
Build date: 2015-03-12 15:35:49-0400

=== Xamarin.Android ===

Version: 4.20.0.38 (Business Edition)
Android SDK: /Users/beyerc/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0.3 (API level 15)
		4.2   (API level 17)
		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

=== Xamarin.Mac ===

Version: 1.12.0.14 (Business Edition)

=== Build Information ===

Release ID: 508000463
Git revision: 0d7bda0c4d692947c71212ef66c3b78434a3db9c
Build date: 2015-03-12 15:17:04-04
Xamarin addins: eea4775e7186e87242800751964b19a8d768276a

=== Operating System ===

Mac OS X 10.10.2
Darwin byrc-mbp.router 14.1.0 Darwin Kernel Version 14.1.0
    Thu Feb 26 19:26:47 PST 2015
    root:xnu-2782.10.73~1/RELEASE_X86_64 x86_64
Comment 1 Sebastien Pouliot 2015-03-16 20:58:05 UTC
Well that's a problem, but not a solution :-) Universal apps will be on the App Store and some will contain watch apps [extensions] since Apple won't let you do otherwise.

@Vincent do you still have some ObjC watch apps lying around ? Could you confirm me that the "main" app can deploy successfully to an iPad running iOS 8.2 ? (even an older 8.x version would be nice to try if you have one around).

I kind of suspect we might be missing some configuration to cover this case. There was (and still is) not much documentation about watch apps versus physical devices. I'm not even 100% sure the current Xcode would be able to deploy to watch hardware without an update...
Comment 2 Sebastien Pouliot 2015-03-16 21:04:18 UTC
Dupe

*** This bug has been marked as a duplicate of bug 28078 ***