Is it a normal/usual/expected practice that a Mac App Store submission of a Safari extension takes 3 weeks to review? No, never. Request an expedited review.

I'm actually seeing the opposite results: your sample extension works for me in Safari Technology Preview 202 but does not work in Safari 17.6.

I've also experienced this issue. As mentioned, there appears to be a bug in App Store Connect Trends where unit sales are double counted starting June 21. I wrote a blog post: https://lapcatsoftware.com/articles/2024/8/2.html

Why does your background listener return true after calling sendResponse? Returning true is for async responses that are called later.

FB11958284 - target="_blank" and command-click don't work in extension pages https://github.com/lapcat/SafariExtensions/issues/35

No, it's not just you. There are a lot of tags missing. For example, https://developer.apple.com/forums/tags/safari-extensions and its corresponding RSS feed are missing.

See this bug, with workaround: https://github.com/lapcat/SafariExtensions/issues/41

I've discovered that this is a bug in Xcode 15 that doesn't correctly handle a symlink from ~/Library/Developer to /Users/Shared/Developer The symlink was never a problem in Xcode 14 and earlier. FB12363725

By the way, I'm maintaining a public list of Safari extension bugs, if anyone is interested in adding theirs here: https://github.com/lapcat/SafariExtensions/issues

By the way, this sounds like a great way to get rejected by App Review: "How you do that depends on how your app is built. With Xcode it’s as simple as enabling a restricted entitlements on your app target." I've gotten rejections in the past for unused entitlements.

Quinn, I just got this warning, but I don't want to use TestFlight for Mac. Is there any way to avoid getting the warning?

This has always worked for me in Safari. Are you using Manifest V2 or V3?

According to Chrome's own documentation, "DOM-based timers, such as window.setTimeout() or window.setInterval(), are not honored in non-persistent background scripts if they trigger when the event page is dormant. Instead, use the alarms API." https://developer.chrome.com/docs/extensions/mv2/background_migration/#timers

The Remote Audio Output Protocol, AKA AirTunes, AKA AirPlay, has been using port 5000 since the year 2004. This is nothing new. All AirPlay receivers including AirPort Express and Apple TV use port 5000. If you've ever used Airfoil on your Mac (Airfoil Speakers was released in 2008), that also uses 5000 for the same reason. AirPlay receiving is new to macOS Monterey, but AirPlay itself is very old, predating Flask and these other web development environments. No, Apple is not trying to make web development difficult.

Update: This Slack channel has been shut down. There was a lot of initial interest, but it never really caught on, and it was mostly quiet after the first couple of weeks. If the Developer Forum moderators could delete my post, I'd appreciate it. I can't seem to do it myself.