Nsextensionpointidentifier Error Only on Real Device

Build watch app to device

Make sure that you've created provisioning profiles for the iOS app, WatchOs2 App and WatchOS2 App Extension (yes, that's three) and make sure the iPhone is in the first and the Watch is in the last two.

You can then use Studio to configure them.

If you use a wildcard provisioning profile for the iOS app and both the iPhone and Watch are in it. Then you can leave the provisioning profiles for the WatchOS2 App and WatchOS2 App extension unconfigured and Titanium will automatically use that of the iOS app. You should see the following in the console log:

[WARN] :   iOS extension "Ti 5.2.0" target "<device>" is missing the Ti 5.2.0 WatchKit App provisioning profile UUID in tiapp.xml.
[WARN] : Using the iOS app provisioning profile UUID "xxxxxxxx-7262-4b24-82cf-7969af384b4b"
[WARN] : iOS extension "Ti 5.2.0" target "<device>" is missing the Ti 5.2.0 WatchKit Extension provisioning profile UUID in tiapp.xml.
[WARN] : Using the iOS app provisioning profile UUID "xxxxxxxx-7262-4b24-82cf-7969af384b4b"

Distributing app to App Store Connect upload fails with invalid NSExtention key error in info.plist

Does your app's Info.plist have an NSExtension key? Only your extension's Info.plist should contain the NSExtension attributes.

Can't run app with NotificationContentExtension in lower target version

I think this is what you want:

if(@available(iOS 10.0, *)) {
// your code here.
}

Apple Watch app installation issue - NSExtensionPointIdentifier

To answer this (using @LoVo's comment) - I fixed the issue by changing the deployment target to 8.2 in the Extension's Build Settings (not in the main app's build settings).

The main app's deployment target can be set at a lower deployment target, mine is now 7.0.



Related Topics



Leave a reply



Submit