When I generate a lighthouse report on my web application, I get this error:
and when I click on the Learn More link, it throws me a 404 error page.
I also tried to google this error message, but I couldn't find anything related to this.
Can anyone tell me why is this happening?
It is a known problem of the extension.
There is an opened issue in the Github of the project.
Related
I've been unable to access the source code for any of my Cloud Functions across multiple Google Cloud Projects for well over a week. When clicking through to the Source tab of a function I see a greyed out area with the message "Unknown error while fetching the archive".
On clicking Edit I'm met with "We can't display source code of this function." The error persists even if I try to set up a new Cloud Function. Then I get an error with no accompanying message.
There doesn't seem to be any issue with billing, I've tried logging in as a different user and I'm unable to find any documentation online. Has anyone been able to resolve this successfully?
In most scenarios, this error arises due to billing issues related to the account. However, since you confirm your case is not so, I suggest you try logging in with an incognito window once.
If it doesn't help, make sure to try out the steps mentioned in here.
I met 404 error when I click the link for the installation of the LibX extension for Google Chrome recently. When I used the google web store to search keyword "libx", it shows that there are no matching results.
I asked several people around and they all met the same issue. Does anyone have any idea of what's going on there and how to fix this problem?
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?
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.
I caught this exception on my ASP.NET project. I don't handle any jquery or javascript error. What is the reason this exception?
I searched all similar problems but all of them are using google extension. But I don't use any extension on my project.
After I caught this exception on my project, opened another project on google chrome I seem similar exception. Maybe problem why reason is google chrome.
Error: extensions::webstore:34 Uncaught Chrome Web Store installations can only be started by the top frame.
It's caused by some embedded iframe calling chrome.webstore API that handles inline installs.
The error basically says "you can't use inline installs from iframes".
Check all embedded frames.
It's also possible that your Chrome has some fishy extension installed that tried to inject frames into your pages. Check if the error reproduces in Incognito.
I got my account whitelisted, and now I should be able to publish my add-on.
I went through the this list: https://developers.google.com/apps-script/add-ons/publish#development_checklist.
But now, when I try to publish it as decribed here: https://developers.google.com/apps-script/add-ons/publish#publish_your_add-on, I get this error message on the developer dashboard:
Please fix the following errors: The manifest has an invalid install
container.
It does not provide much information to me, so i don't know what to do with it.
Can someone tell me how to start?
The same question was published recently on "google-apps-script-issues" bugtracker.
Google aknowledged it as a "whitelist" problem:
https://code.google.com/p/google-apps-script-issues/issues/detail?id=4000
The best I can do now is wait.. As suggested on the issue page, if somebody will have the same problem they should star the issue.