Debug your Safari App Extension with these techniques.
Here are a few options for debugging your Safari App Extension:
Check website access permissions. Make sure your website access permissions and allowed domain patterns are right. For more details, see Adjusting Website Access Permissions.
Check URL patterns. Make sure your URL patterns are right. For more details, see URL Patterns.
Update the deployment target. Check that the deployment target for your app is set to the system you are testing on.
Verify that your extension is visible to Safari. In the Terminal app, type the following command:
console command to print messages to the Safari debugging console:
Log messages to the system console. In the native environment, calls to
NSLog from within your Safari App Extension are sent to the system console and are visible in the Console app. You can also filter for other messages using the name of your app extension. For example, if your app extension is terminated because of an error, a message is sent to the Console and a crash log is generated.
Ensure that the Safari app extension is enabled. Many Safari App Extensions provide a standalone experience that’s completely independent of the containing app. In other cases, the reason for providing the Safari App Extension is to integrate content from your app into the Safari web experience. To integrate content, you need to share information between your app and app extension, and to do so, you need to ensure that your extension is enabled. For security reasons, when your app is installed on a system, its Safari App Extensions aren’t automatically enabled; the end user must explicitly enable each extension. Use your app to check to see whether one of its app extensions has been enabled and, if necessary, display the app extension’s Safari preferences panel so the end user can enable it.