I used to have a provisioning profile with an appropriate wildcard application identifier (*) to sign a bunch of applications for clients. Each explicit application identifier is declared in the Bundle ID field in the Xcode project. The problem is that every application uses the wireless settings feature. According to Apple ( https://developer.apple.com/library/ios/qa/qa1713/_index.html )
Since the application identifier defines a unique configuration of rights, Wildcard application identifiers are intended for use when signing code for all applications that do not support the application features.
Prior to Xcode 7.3, this was not a big deal; it always worked. After upgrading to the latest public beta of Xcode 8.0, I can no longer encode my applications using the wildcard application identifier associated with my provisioning profile, and I cannot add explicit application identifiers because they are already managed by clients. When I try to use a new function of automatic code signing, it tells me that the application identifier that I proposed in the Bundle field of my Xcode project cannot be registered with my development team (con Of course not!), because it belongs to a team of clients that I am not a member of).
If I click the disclosure button next to the Xcode managed profile, the only problem I see is the inability to configure a wireless accessory
So, can I ask the client to add this feature to the explicit identifier of the application to solve this problem?
If I try to code the application directly in the build settings using the old method with my provisioning profile (which I restored again), I always get the following problem:
An “application” is not a code, but requires rights. It is not possible to add rights to a binary file without signing it.
Signing code is required for the product type "Application" in the SDK "iOS 10.0"
Can someone help me solve this problem? I've been stuck since.