New “currentURL is not defined” Error in Google Apps Script Web Apps












8















A few days ago this started appearing in my Google Apps Script Web App Consoles:




Uncaught (in promise) ReferenceError: currentURL is not defined at then.catch.e (content_script_bundle.js:13)




What might this be?










share|improve this question

























  • It is just a bunch of minified script.

    – webstermath
    Nov 28 '18 at 23:24
















8















A few days ago this started appearing in my Google Apps Script Web App Consoles:




Uncaught (in promise) ReferenceError: currentURL is not defined at then.catch.e (content_script_bundle.js:13)




What might this be?










share|improve this question

























  • It is just a bunch of minified script.

    – webstermath
    Nov 28 '18 at 23:24














8












8








8


2






A few days ago this started appearing in my Google Apps Script Web App Consoles:




Uncaught (in promise) ReferenceError: currentURL is not defined at then.catch.e (content_script_bundle.js:13)




What might this be?










share|improve this question
















A few days ago this started appearing in my Google Apps Script Web App Consoles:




Uncaught (in promise) ReferenceError: currentURL is not defined at then.catch.e (content_script_bundle.js:13)




What might this be?







google-apps-script web-applications






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 '18 at 20:14









TheMaster

10.6k3936




10.6k3936










asked Nov 28 '18 at 19:58









webstermathwebstermath

13329




13329













  • It is just a bunch of minified script.

    – webstermath
    Nov 28 '18 at 23:24



















  • It is just a bunch of minified script.

    – webstermath
    Nov 28 '18 at 23:24

















It is just a bunch of minified script.

– webstermath
Nov 28 '18 at 23:24





It is just a bunch of minified script.

– webstermath
Nov 28 '18 at 23:24












1 Answer
1






active

oldest

votes


















16














content_script_bundle.js is likely a script within a Chrome Extension. Ghostery has such a js file. Basically, it has caught an error of some kind



window.console.error("Could not run content script", e, currentURL()) 


Unfortunately, the line in the script that pushes the error to the console itself has a minor bug whereby currentURL has not been defined so it squawks.



Just turn off Ghostery or whatever and the error will disappear. Although, you can just ignore it. Easiest though is to right-click the console message and select "Hide messages from content_script_bundle.js" if it's bothering you. If it is Ghostery then mark your site as trusted as noted in the comment below. Probably the best solution.



This is a screenshot from Chrome Inspector.



enter image description here






share|improve this answer





















  • 3





    You can mark your site as trusted in Ghostery and the error disappears

    – besthost
    Dec 13 '18 at 11:23












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%2f53527188%2fnew-currenturl-is-not-defined-error-in-google-apps-script-web-apps%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









16














content_script_bundle.js is likely a script within a Chrome Extension. Ghostery has such a js file. Basically, it has caught an error of some kind



window.console.error("Could not run content script", e, currentURL()) 


Unfortunately, the line in the script that pushes the error to the console itself has a minor bug whereby currentURL has not been defined so it squawks.



Just turn off Ghostery or whatever and the error will disappear. Although, you can just ignore it. Easiest though is to right-click the console message and select "Hide messages from content_script_bundle.js" if it's bothering you. If it is Ghostery then mark your site as trusted as noted in the comment below. Probably the best solution.



This is a screenshot from Chrome Inspector.



enter image description here






share|improve this answer





















  • 3





    You can mark your site as trusted in Ghostery and the error disappears

    – besthost
    Dec 13 '18 at 11:23
















16














content_script_bundle.js is likely a script within a Chrome Extension. Ghostery has such a js file. Basically, it has caught an error of some kind



window.console.error("Could not run content script", e, currentURL()) 


Unfortunately, the line in the script that pushes the error to the console itself has a minor bug whereby currentURL has not been defined so it squawks.



Just turn off Ghostery or whatever and the error will disappear. Although, you can just ignore it. Easiest though is to right-click the console message and select "Hide messages from content_script_bundle.js" if it's bothering you. If it is Ghostery then mark your site as trusted as noted in the comment below. Probably the best solution.



This is a screenshot from Chrome Inspector.



enter image description here






share|improve this answer





















  • 3





    You can mark your site as trusted in Ghostery and the error disappears

    – besthost
    Dec 13 '18 at 11:23














16












16








16







content_script_bundle.js is likely a script within a Chrome Extension. Ghostery has such a js file. Basically, it has caught an error of some kind



window.console.error("Could not run content script", e, currentURL()) 


Unfortunately, the line in the script that pushes the error to the console itself has a minor bug whereby currentURL has not been defined so it squawks.



Just turn off Ghostery or whatever and the error will disappear. Although, you can just ignore it. Easiest though is to right-click the console message and select "Hide messages from content_script_bundle.js" if it's bothering you. If it is Ghostery then mark your site as trusted as noted in the comment below. Probably the best solution.



This is a screenshot from Chrome Inspector.



enter image description here






share|improve this answer















content_script_bundle.js is likely a script within a Chrome Extension. Ghostery has such a js file. Basically, it has caught an error of some kind



window.console.error("Could not run content script", e, currentURL()) 


Unfortunately, the line in the script that pushes the error to the console itself has a minor bug whereby currentURL has not been defined so it squawks.



Just turn off Ghostery or whatever and the error will disappear. Although, you can just ignore it. Easiest though is to right-click the console message and select "Hide messages from content_script_bundle.js" if it's bothering you. If it is Ghostery then mark your site as trusted as noted in the comment below. Probably the best solution.



This is a screenshot from Chrome Inspector.



enter image description here







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 7 at 2:18

























answered Nov 29 '18 at 3:22









GazzerGazzer

2,40692937




2,40692937








  • 3





    You can mark your site as trusted in Ghostery and the error disappears

    – besthost
    Dec 13 '18 at 11:23














  • 3





    You can mark your site as trusted in Ghostery and the error disappears

    – besthost
    Dec 13 '18 at 11:23








3




3





You can mark your site as trusted in Ghostery and the error disappears

– besthost
Dec 13 '18 at 11:23





You can mark your site as trusted in Ghostery and the error disappears

– besthost
Dec 13 '18 at 11:23




















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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53527188%2fnew-currenturl-is-not-defined-error-in-google-apps-script-web-apps%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

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)