Adding ExternalAccessory Framework should not require the Wireless Accessory Configuration entitlement

Originator:logan.b.jones
Number:rdar://27854513 Date Originated:15-Aug-2016 02:46 PM
Status:Open Resolved:
Product:Developer Tools Product Version:Xcode-beta (8S201h)
Classification:Other Bug Reproducible:Always
 
This is a duplicate of rdar://19565319

Summary:
As of iOS 10/Xcode 8, an app to which I've heretofore linked the ExternalAccessory framework now triggers errors in the General>Signing tab.

I'm not using the ExternalAccessory.framework for wireless accessory configuration; it supports bluetooth and directly-connected devices. I don't think it should fail to build or automatically switch on this capability.

If I attempt remove this capability, it re-toggles the capability back on. If i remove ExternalAccessory.framework then the signing error is cleared; but the project will now fail to link (of course). Once the ExternalAccessory.framework is added back into the link section, the WAC capability is automatically toggled on and the signing error returns.

Steps to Reproduce:
* Create a new project
* Add the ExternalAccessory.framework to the list of Linked Frameworks and Libraries.

Expected Results:
The Wireless Accessory Configuration capability should not be turned on.

Actual Results:
The Wireless Accessory Configuration capability is turned on.

Version:
Observed in Xcode 8 (all betas up to 8S201h).

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!