How to troubleshoot when Safari App Extension not appear in Safari Preferences?

Question

Created Dec ’18

Replies 12

Boosts 0

Views 5k

Participants 12

I'm developing a Safari App Extension. Previously it worked fine. When I run the project in Xcode, and enable Allow Unsigned Extensions in Safari, I can see my extension in Safari Preferences -> Extensions page.

After I merged code with one of my team member, suddenly the Extension cannot get installed.

I have tried:

Clean the build folder in Xcode, and run again. But no luck.
Restart Xcode doesn't help either.
Use command
```
pluginkit -mAvvv -p com.apple.Safari.extension
```
to check installed Safari extensions list. My extension is not in the list.

There are some errors in Xcode output, but I can't link them with the issue I'm facing:

objc[59117]: Class AMSupportURLConnectionDelegate is implemented in both /System/Library/PrivateFrameworks/EmbeddedOSInstall.framework/Versions/A/EmbeddedOSInstall (0x7fff9a2aa748) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1063e8600). One of the two will be used. Which one is undefined.

objc[59117]: Class AMSupportURLSession is implemented in both /System/Library/PrivateFrameworks/OSPersonalization.framework/Versions/A/OSPersonalization (0x7fff9b5d49f0) and /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/MobileDevice (0x1063e8650). One of the two will be used. Which one is undefined.

2018-12-13 17:28:16.710744+0800 Safari[59117:1304953] Could not connect action, target class SecurityPreferences does not respond to -toggleJavaScriptCanOpenWindows:

2018-12-13 17:28:16.833463+0800 Safari[59117:1304953] AssertMacros: 0 (value = 0x0), file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/BiometricKit/BiometricKit-75.71.1/BiometricKit/BiometricKitXPCClient.m, line: 75

2018-12-13 17:28:16.833544+0800 Safari[59117:1304953] AssertMacros: 0 (value = 0x0), file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/BiometricKit/BiometricKit-75.71.1/BiometricKit/BiometricKitXPCClient.m, line: 396

2018-12-13 17:28:16.833650+0800 Safari[59117:1304953] [Framework-Internal-Legacy] AssertMacros: _xpcClient (value = 0x0), file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/BiometricKit/BiometricKit-75.71.1/BiometricKit/BiometricKit.m, line: 137

2018-12-13 17:28:17.300775+0800 Safari[59117:1304985] [RemotePlistController] The downloaded plist could not be loaded: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

2018-12-13 17:28:17.841024+0800 Safari[59117:1304996] NSURLConnection finished with error - code -1100

2018-12-13 17:28:18.008953+0800 Safari[59117:1305029] [CrowdsourcedAutoFill] Unable to read cloud AutoFill correction sets, error: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

2018-12-13 17:28:18.049658+0800 Safari[59117:1305028] [CloudBookmarks] Error fetching remote migration state: Error Domain=com.apple.SafariBookmarksSync.CloudBookmarksErrorDomain Code=0 "(null)"

2018-12-13 17:28:18.521444+0800 Safari[59117:1305032] NSURLConnection finished with error - code -1100

2018-12-13 17:28:18.544894+0800 Safari[59117:1305188] [RemotePlistController] The downloaded plist could not be loaded: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

2018-12-13 17:28:18.659265+0800 Safari[59117:1305029] Calling IOPPFGetProperty simulator_utility_clamp!

2018-12-13 17:28:18.957830+0800 Safari[59117:1304953] [WebKit2Callbacks] Page (pid: 59135) did become unresponsive

2018-12-13 17:28:19.684984+0800 Safari[59117:1304953] [WebKit2Callbacks] Page (pid: 59135) did become responsive

2018-12-13 17:28:19.790156+0800 Safari[59117:1304997] [RemotePlistController] The downloaded plist could not be loaded: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

2018-12-14 10:49:13.324838+0800 Safari[59117:1324361] [CrowdsourcedAutoFill] Unable to read cloud AutoFill correction sets, error: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

2018-12-14 10:49:13.415684+0800 Safari[59117:1326314] [CrowdsourcedAutoFill] Unable to read cloud AutoFill correction sets, error: Error Domain=NSCocoaErrorDomain Code=260 "The file couldn’t be opened because it doesn’t exist."

Now I'm running out of options. It lacks official documentation in Apple Developer site.

Is there regular steps to troubleshoot this kind of issue? Is there any kind of system logs which can help me address the error? Any suggestion is appreciated.

Boost

Answer 1

hmpro74 OP

Dec ’18

I have tried everything in Apple's official Troubleshooting Safari App Extension page at https://developer.apple.com/documentation/safariservices/safari_app_extensions/troubleshooting_your_safari_app_extension

In the section:

Verify that your extension is visible to Safari. In the Terminal app, type the following command:

pluginkit -mAvvv -p com.apple.Safari.extension

It only shows how to check if extension is visible to Safari, but doesn't shows how to continue troubleshoot if the extension is not visible to Safari. BTW, I have enabled "Allow Unsigned Extensions".

What should I do when my extension is not visible to Safari, and there is none related error in Xcode?

1

Answer 2

jeffjenkins OP

Dec ’18

I have an almsot equivalent error message for the default Safari extension loaded in developer mode.

OSX 10.14.1

Xcode 10.1

0

Answer 3

Micro Focus OP

Apr ’19

We also encount that problem, It just thward us for several weeks, Does anyone know how to resolve that, Thanks

0

Answer 4

Fabasoft OP

Nov ’19

Hello!
I encountered this problem on macOS Catalina in combaination with app notariziation and hardened runtime capiability.

Enabling the hardened runtime capability caused all extensions to be not recognized, even the app was correctly signed, regardless of app notarization, so I disabled it and now it works.

Regards,

Dominik

1

Answer 5

Engineer OP

Apple

Nov ’19

If the output of the pluginkit doesn't list your extension, then Safari will have no way to know about it.

If you see this, please provide feedback using Feedback Assistant and file an issue. Once you do that, if you put the feedback ID in here I can look at it and follow up.

Thanks!

0

Answer 6

pkdavidstorm OP

Dec ’20

I still have the same question as @hmpro74. My extension is not visible to Safari and I have been unable to find any troubleshooting steps.

1

Answer 7

tuggif OP

Dec ’20

Some of my users are having this same issue. They have the latest version of Big Sur and Safari 14, yet are unable to see the extension in their Safari Preferences. It’s like it’s unable to install for them.

1

Answer 8

ioarch OP

Jan ’21

any resolution on this? Using M1 MBP Big Sur and Safari doesn't show a few extensions downloaded off MAS

0

Answer 9

carlosj OP

Mar ’21

I got several users of reporting some extensions are missing in preferences as well. How can this be resolved?

0

Answer 10

Manpek OP

Apr ’21

Confirming the previous post by carlosj. He developed an extension that does not appear in safari preferences.
Config is
Mac OS 10.14.6 Mojave with Safari 14.0.3

0

Answer 11

kmadhavan OP

Jun ’21

Also receiving this issue after installing macOS Monterey. Is there a fix coming?

0

Answer 12

innovinityLabs OP

Jun ’21

am having same problem with AutoHD extension. not showing up in safari and running that command too.

1