Browser tab query “Receiving end does not exist” which works on chrome












0














Background script



browser.runtime.onMessage.addListener(function (event) {
if( event.type === 'authenticate' ) {
browser.tabs.query({active: true}, function(tab) {
browser.tabs.sendMessage(tab[0].id, {
method: 'main',
auth0: "test"
}, function() {});
});
}
});


Content script



browser.runtime.sendMessage({
type: "authenticate"
});

browser.extension.onMessage.addListener(function(request, sender, sendResponse) {
if( request.method == 'main' ) {
login();
} else if( request.method == 'logout' ) {
logout();
}
sendResponse({});
});


The event goes through and the tab id is correct, but the debug info from firefox shows "Error: Could not establish connection. Receiving end does not exist."



On chrome the event callback goes through. Anyone know what the issue is? Looking through google I found something about the id not being correct but I'm not sure what the issue is here.










share|improve this question






















  • You're sending a new message to the active tab, but an instance of the content script runs in each matching tab, not just the active one. Simply respond to the sender directly as shown in the messaging documentation (see examples with sendResponse).
    – wOxxOm
    Nov 22 at 18:23












  • Thanks for the comment
    – Robert
    Nov 22 at 18:35










  • browser.extension.onMessage shouldn't even exist; chrome.extension.onMessage is deprecated in Chrome and I doubt Mozilla copied it to the browser namespace. Use browser.runtime.onMessage instead.
    – Xan
    Nov 23 at 11:05












  • Yup, that fixed it.
    – Robert
    Nov 23 at 19:52
















0














Background script



browser.runtime.onMessage.addListener(function (event) {
if( event.type === 'authenticate' ) {
browser.tabs.query({active: true}, function(tab) {
browser.tabs.sendMessage(tab[0].id, {
method: 'main',
auth0: "test"
}, function() {});
});
}
});


Content script



browser.runtime.sendMessage({
type: "authenticate"
});

browser.extension.onMessage.addListener(function(request, sender, sendResponse) {
if( request.method == 'main' ) {
login();
} else if( request.method == 'logout' ) {
logout();
}
sendResponse({});
});


The event goes through and the tab id is correct, but the debug info from firefox shows "Error: Could not establish connection. Receiving end does not exist."



On chrome the event callback goes through. Anyone know what the issue is? Looking through google I found something about the id not being correct but I'm not sure what the issue is here.










share|improve this question






















  • You're sending a new message to the active tab, but an instance of the content script runs in each matching tab, not just the active one. Simply respond to the sender directly as shown in the messaging documentation (see examples with sendResponse).
    – wOxxOm
    Nov 22 at 18:23












  • Thanks for the comment
    – Robert
    Nov 22 at 18:35










  • browser.extension.onMessage shouldn't even exist; chrome.extension.onMessage is deprecated in Chrome and I doubt Mozilla copied it to the browser namespace. Use browser.runtime.onMessage instead.
    – Xan
    Nov 23 at 11:05












  • Yup, that fixed it.
    – Robert
    Nov 23 at 19:52














0












0








0







Background script



browser.runtime.onMessage.addListener(function (event) {
if( event.type === 'authenticate' ) {
browser.tabs.query({active: true}, function(tab) {
browser.tabs.sendMessage(tab[0].id, {
method: 'main',
auth0: "test"
}, function() {});
});
}
});


Content script



browser.runtime.sendMessage({
type: "authenticate"
});

browser.extension.onMessage.addListener(function(request, sender, sendResponse) {
if( request.method == 'main' ) {
login();
} else if( request.method == 'logout' ) {
logout();
}
sendResponse({});
});


The event goes through and the tab id is correct, but the debug info from firefox shows "Error: Could not establish connection. Receiving end does not exist."



On chrome the event callback goes through. Anyone know what the issue is? Looking through google I found something about the id not being correct but I'm not sure what the issue is here.










share|improve this question













Background script



browser.runtime.onMessage.addListener(function (event) {
if( event.type === 'authenticate' ) {
browser.tabs.query({active: true}, function(tab) {
browser.tabs.sendMessage(tab[0].id, {
method: 'main',
auth0: "test"
}, function() {});
});
}
});


Content script



browser.runtime.sendMessage({
type: "authenticate"
});

browser.extension.onMessage.addListener(function(request, sender, sendResponse) {
if( request.method == 'main' ) {
login();
} else if( request.method == 'logout' ) {
logout();
}
sendResponse({});
});


The event goes through and the tab id is correct, but the debug info from firefox shows "Error: Could not establish connection. Receiving end does not exist."



On chrome the event callback goes through. Anyone know what the issue is? Looking through google I found something about the id not being correct but I'm not sure what the issue is here.







javascript google-chrome-extension firefox-addon






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 at 18:07









Robert

99111




99111












  • You're sending a new message to the active tab, but an instance of the content script runs in each matching tab, not just the active one. Simply respond to the sender directly as shown in the messaging documentation (see examples with sendResponse).
    – wOxxOm
    Nov 22 at 18:23












  • Thanks for the comment
    – Robert
    Nov 22 at 18:35










  • browser.extension.onMessage shouldn't even exist; chrome.extension.onMessage is deprecated in Chrome and I doubt Mozilla copied it to the browser namespace. Use browser.runtime.onMessage instead.
    – Xan
    Nov 23 at 11:05












  • Yup, that fixed it.
    – Robert
    Nov 23 at 19:52


















  • You're sending a new message to the active tab, but an instance of the content script runs in each matching tab, not just the active one. Simply respond to the sender directly as shown in the messaging documentation (see examples with sendResponse).
    – wOxxOm
    Nov 22 at 18:23












  • Thanks for the comment
    – Robert
    Nov 22 at 18:35










  • browser.extension.onMessage shouldn't even exist; chrome.extension.onMessage is deprecated in Chrome and I doubt Mozilla copied it to the browser namespace. Use browser.runtime.onMessage instead.
    – Xan
    Nov 23 at 11:05












  • Yup, that fixed it.
    – Robert
    Nov 23 at 19:52
















You're sending a new message to the active tab, but an instance of the content script runs in each matching tab, not just the active one. Simply respond to the sender directly as shown in the messaging documentation (see examples with sendResponse).
– wOxxOm
Nov 22 at 18:23






You're sending a new message to the active tab, but an instance of the content script runs in each matching tab, not just the active one. Simply respond to the sender directly as shown in the messaging documentation (see examples with sendResponse).
– wOxxOm
Nov 22 at 18:23














Thanks for the comment
– Robert
Nov 22 at 18:35




Thanks for the comment
– Robert
Nov 22 at 18:35












browser.extension.onMessage shouldn't even exist; chrome.extension.onMessage is deprecated in Chrome and I doubt Mozilla copied it to the browser namespace. Use browser.runtime.onMessage instead.
– Xan
Nov 23 at 11:05






browser.extension.onMessage shouldn't even exist; chrome.extension.onMessage is deprecated in Chrome and I doubt Mozilla copied it to the browser namespace. Use browser.runtime.onMessage instead.
– Xan
Nov 23 at 11:05














Yup, that fixed it.
– Robert
Nov 23 at 19:52




Yup, that fixed it.
– Robert
Nov 23 at 19:52












1 Answer
1






active

oldest

votes


















0














Using browser.runtime.onMessage and changing



browser.tabs.query({active: true}, function(tab) {
browser.tabs.sendMessage(tab[0].id, {
method: 'main',
auth0: "test"
}, function() {});
});


to



browser.tabs.query({active: true, currentWindow: true}, function(tab) {
chrome.tabs.sendMessage(tab[0].id, {
method: 'main',
auth0: "test"
});
});


fixed it for me.






share|improve this answer





















    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53436260%2fbrowser-tab-query-receiving-end-does-not-exist-which-works-on-chrome%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Using browser.runtime.onMessage and changing



    browser.tabs.query({active: true}, function(tab) {
    browser.tabs.sendMessage(tab[0].id, {
    method: 'main',
    auth0: "test"
    }, function() {});
    });


    to



    browser.tabs.query({active: true, currentWindow: true}, function(tab) {
    chrome.tabs.sendMessage(tab[0].id, {
    method: 'main',
    auth0: "test"
    });
    });


    fixed it for me.






    share|improve this answer


























      0














      Using browser.runtime.onMessage and changing



      browser.tabs.query({active: true}, function(tab) {
      browser.tabs.sendMessage(tab[0].id, {
      method: 'main',
      auth0: "test"
      }, function() {});
      });


      to



      browser.tabs.query({active: true, currentWindow: true}, function(tab) {
      chrome.tabs.sendMessage(tab[0].id, {
      method: 'main',
      auth0: "test"
      });
      });


      fixed it for me.






      share|improve this answer
























        0












        0








        0






        Using browser.runtime.onMessage and changing



        browser.tabs.query({active: true}, function(tab) {
        browser.tabs.sendMessage(tab[0].id, {
        method: 'main',
        auth0: "test"
        }, function() {});
        });


        to



        browser.tabs.query({active: true, currentWindow: true}, function(tab) {
        chrome.tabs.sendMessage(tab[0].id, {
        method: 'main',
        auth0: "test"
        });
        });


        fixed it for me.






        share|improve this answer












        Using browser.runtime.onMessage and changing



        browser.tabs.query({active: true}, function(tab) {
        browser.tabs.sendMessage(tab[0].id, {
        method: 'main',
        auth0: "test"
        }, function() {});
        });


        to



        browser.tabs.query({active: true, currentWindow: true}, function(tab) {
        chrome.tabs.sendMessage(tab[0].id, {
        method: 'main',
        auth0: "test"
        });
        });


        fixed it for me.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 23 at 19:54









        Robert

        99111




        99111






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53436260%2fbrowser-tab-query-receiving-end-does-not-exist-which-works-on-chrome%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            What visual should I use to simply compare current year value vs last year in Power BI desktop

            Alexandru Averescu

            Trompette piccolo