@tylerdurden101390 WOW it worked, thank you so much! I would not have figured it out without this code example haha. You are a gentleman and a scholar.

My extension also relies on content.js and background.js for its Settings page, and unfortunately, looks like public Sequoia/Safari 18 broke its Settings page - my users made sure to let me know! Hoping this is fixed ASAP. How did you set up the workaround code-wise? Something like the following? remove "content_scripts" section from manifest.json run the content script programmatically.

This worked beautifully, thank you!

Hi @bweinstein, I'm having to ask multiple users a day to do the following two terminal commands to fix their Safari extensions not showing up, is there any way that this can be fixed? The following two commands work with a 100% success rate, but they have to do it on their end unfortunately. PATH=/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support:"$PATH" lsregister -f /Applications/Safari.app

Thank you for your quick reply, Eskimo! I'm in direct contact with App Review now, hopefully this will be resolved shortly. (There are so many auto-clickers on the Mac App Store, it seems like it's an all-or-nothing type of deal haha.)

One of my users reported back saying that the two lsregister terminal commands worked!! Finally! Is there a reason why some users are experiencing this issue (Safari Launch Services needing to be force updated?) Thanks!

Yes! Check out the accepted answer (lsregister).

AMAZING, IT WORKED! THANK YOU SO MUCH FOR THIS!

Sorry just saw this comment and this new lsregister solution. I just asked a user experiencing this issue to try it out - will report back!

Unfortunately I have not, however, I just asked one user experiencing this issue to try out this new lsregister solution - will report back with results!