chrome.runtime.onMessage sendResponse async not working

Question

Created Dec ’22

Replies 5

Boosts 0

Views 2.7k

Participants 3

My background script is listening for chrome.runtime.onMessage and it needs to do run an async function before sending the response i.e.

chrome.runtime.onMessage.addListener(function (
  message,
  sender,
  sendResponse
) {
  setTimeout(() => {
    sendResponse("response")
  }, 100);

  return true;
})

The MDN docs for this say that returning true should allow sendResponse to happen asynchronously, and it works in our chrome extension. But in safari the content script is never getting the response.

Sending the response without async works fine.

My safari version is Version 16.1 (17614.2.9.1.13, 17614) This is a V3 manifest chrome extension that we are using xcrun safari-web-extension-converter to convert to safari

Is there a workaround for this?

Boost

Answer 1

jeffjohnson OP

Dec ’22

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

0

Answer 2

jhulme-ut OP

Dec ’22

Ah sorry, that was just a simple example to try help reproduce, I'm not doing a timer in our actual code.

chrome.runtime.onMessage.addListener(function (
  message,
  sender,
  sendResponse
) {
  chrome.storage.local.set({"foo": 1})
    .then(() => {
      sendResponse('response');
    })

  return true;
});

has the same issue

0

Answer 3

jeffjohnson OP

Dec ’22

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

0

Answer 4

jhulme-ut OP

Dec ’22

V3

0

Answer 5

travelarrow OP

May ’23

Hey, are you still running into this issue? I have been running into the same bug. However, manifest v2 and v3 both do not work for me :(

0