![]() It responses to any message from popup.js. This extension requires a 1Password membership. It's updated frequently with less-tested features and improvements, and is intended to be used alongside the nightly channel of the 1Password desktop app. The solution is to return true in background message listener. The 1Password nightly is for adventurous folks who enjoy living on the cutting edge. Although what is described is an attack against the communication between 1Password mini and the browser extension through specialized malware, using the 1Password browser extension protects you from a more typical malware attack of pasteboard/clipboard sniffers. I had same problem when responding on message in callback. Keep using the 1Password browser extension. The next time you visit that site, 1Password will offer to sign you. ![]() When you sign in to or sign up for an account with your Google, Facebook, Microsoft, Apple, Twitter, Okta, or GitHub credentials, 1Password will ask if you’d like to save the login to one of your vaults. [Thanks is rather old and not closely related to Chrome extensions development, but let it be here. Sign in to your favorite sites using Google, Apple, and other providers. ![]() Some of them probably need to start returning promises (marking them as async should be enough). So bottom line, if you see your extension causing these errors - inspect closely all your onMessage listeners. Webextension-polyfill authors have already written about it in June 2018. When you send an async response but fail to use either of these mechanisms, the supplied sendResponse argument to sendMessage goes out of scope and the result is exactly as the error message says: your message port (the message-passing apparatus) is closed before the response was received. When you have the response (or reject it in case of an error). return a Promise from the event listener, and resolve.This keeps the sendResponseįunction valid after the listener returns, so you can call it later. To send an asynchronous response, there are two options: The issue is most likely a mishandled async response to ndMessage. The issue isn't CORB (as another answer here states) as blocked CORs manifest as warnings like -Ĭross-Origin Read Blocking (CORB) blocked cross-origin response In case you're an extension developer who googled your way here trying to stop causing this error:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |