Hi there, one year later and we're experiencing this problem on my team as well. Any luck lu.xu? Or can anyone from Apple comment on this? Sounds like a bug. Thanks, Tyler

I've just noticed the same behavior. In fact-- instead of getting the disconnect, I'm getting an additional connection request from browser action (even though it's not open). Almost like some phantom instance has been opened.

I've reported this issue in this thread as well https://developer.apple.com/forums/thread/671649. bweinstein claims this was fixed, but it still hasn't been. Hoping he or @timothy.hatcher can clarify or provide an update.

Update: I filed an issue with Feedback Assistant back when I initially discovered this issue. They reached out and this appears to be fixed on the latest developer beta for Sequoia macOS 15.

Thank you for addressing this, the workaround appears to fix the problem on Safari 18 / Sequoia RC. Will this be included in the public Sequoia release next Monday, 9/16?

@tuggif No need to remove the content script from the manifest. Here's an update to the snippets I posted that would fix the problem: content.js: const port = chrome.runtime.connect({ name: 'TEST' }) // SEND MESSAGE IMMEDIATELY port.postMessage({type: 'ANYTHING'}) port.onMessage.addListener((message) => { console.log('RECEIVED TEST MESSAGE', message) }) background.js: let canSendMessage = false; chrome.runtime.onConnect.addListener((port) => { if (port.name !== 'TEST') return console.log('test port connected', port) port.onMessage.addListener((message) => { // PORT RECEIVED A MESSAGE, NOW WE CAN RESPOND canSendMessage = true console.log('SENDING PORT MESSAGE') port.postMessage('HELLO') }) })

I'm having this same issue, but with StoreKit 1, also on macOS, for what it's worth. Would be great to see this fixed, there seems to be no way to test purchases initiated outside the app without this.

Mozilla will be landing this change in Firefox soon: https://bugzilla.mozilla.org/show_bug.cgi?id=1956484. Chromium already supports this behavior, as I already noted in the original request. It would be great to get parity across the extension platforms and continue to promote passkeys as the preferred authentication mechanism over passwords. Just to clarify the functionality being requested: Safari extensions should be able to create and use passkeys for domains that they are associated with or have host permissions for. So, for example, instead of only being able to use passkeys bound to a ephemeral Safari Extension origin (i. e. safari-web-extension://UUID), to use passkeys bound to the company's domain (i. e. example.com). I've yet to hear back in Feedback Assistant. How can I better escalate this feature request?