GeezerVison is showing github.com — Unexplained "Error checking for update" · Issue #3182 · greasemonkey/greasemonkey
Unexplained "Error checking for update" #3182DescriptionHi everyone and thank you for making Greasemonkey! I have been a Firefox user for nearly two decades, and heard of Greasemonkey many many times, but never actually used it – until now. Feels like a great tool to have!
I wrote a simple "hello world" script:
// ==UserScript==
// @name Hello
// @version 1
// @grant none
// ==UserScript==
alert('hello greasemonkey');
It works fine, but does not update. When I go to plugins → Greasemonkey → User scripts for this tab → User script options → Update now, I'm getting Error checking for update.
- The error appears under the Update button immediately, as if no network request to my actual script is even attempted
- Nothing is reported in the browser console or in the network requests debugger
- This also happens also if I have
@updateURL and @downloadURL in the script
Is there a place where I can see a more verbose output maybe? Or can the error be made more specific? Reacted by Nathan Phillip Brink Activitymakyen commented on Feb 21, 2024 What you've provided implies that you wrote the userscript in the Greasemonkey editor, rather than installing it from a URL, so Greasemonkey wouldn't have been able to get the URL during the install process. The userscript header you've shown here has nothing defined which would provide any clue to Greasemonkey as to where it should be looking for updates to the userscript, so, of course, updates will fail.
You haven't provided what you actually put in the userscript for @updateURL or @downloadURL, so there's no way for us to say anything as to if what you used should have worked.
Given the general confusion that's involved with looking at output from browser extensions, it's likely you're looking in the wrong place for such output. I haven't reread them recently, but my answers on Stack Overflow: answer to: "How do I see the console.log output of a background script in a Firefox WebExtension?" and answer to: "How to open the correct devtools console to see output from an extension script?" should at least be pointing in the right general direction for how to view an appropriate console. Cerberus-tm commented on Feb 21, 2024 makyen commented on Feb 21, 2024 @Cerberus-tm Yes, that appears to be outdated. They seem to have removed that option and added a "Browser Console Mode" banner where you can select "Parent process only (Fast)" or "Multiprocess (Slower)". Unfortunately, they also appear to have broken it in that it refuses to not scroll with newly added information, even if you've manually scrolled back to some point in time (which should, but doesn't, remain static in the display at the point you've scrolled back to). In "Multiprocess (Slower)" mode it also appears to be a concatenation of all Web Consoles, which is largely unusable due to the scrolling issue (i.e., in an actively used profile, I wasn't able to even scroll back to look at something specific without it scrolling off the screen). In other words, in that mode on a profile with many tabs, it's a firehose of information which you can't stop and look at a single point (which you used to be able to do). That mode of the Browser Console could still be useful for some things, particularly in a test profile, but not if there are multiple things going on in an actively used profile under normal conditions.
So, for a single extension's background pages you're better off by focusing just on that extension's pages, which can be inspected through about:debugging. arantius commented on Feb 21, 2024 On Wed, Feb 21, 2024 at 1:27 PM Makyen ***@***.***> wrote:
What you've provided implies that you wrote the userscript in the
Greasemonkey editor, rather than installing it from a URL, so Greasemonkey
wouldn't have been able to get the URL during the install process.
I made the same inference, which if correct then I agree: this is the
answer. We should probably just hide the whole "check for update" menu
item when it's impossible to check.
You haven't provided what you actually put in the userscript for @updateURL
I was going to link the relevant docs, but they don't exist because:
Greasemonkey does not support either of those (so they're not documented).
They'd make no difference. Updates are checked for from the original
install URL only. Which is why a locally created script, with no install
URL, can't be updated this way.
…Reacted by Nathan Phillip Brink Cerberus-tm commented on Feb 22, 2024 @makyen Actially, I can scroll back just fine, and it stayed in the scrolled position even if new lines appear at the bottom. So I wonder what is going on in your profile.
About "Show Content Messages": is there now no way to show those? Or are they always shown now? miftygusein commented on Feb 22, 2024
What you've provided implies that you wrote the userscript in the Greasemonkey editor, rather than installing it from a URL
I am sorry for the confusion, I actually hosted it on a website having a .user.js public URL and installed it from there
You haven't provided what you actually put in the userscript for @updateURL or @downloadURL, so there's no way for us to say anything as to if what you used should have worked.
In both of those directives I had the URL I installed the script from. To ensure I did not make any typos, I actually copied it from the browser, after successfully installing from it first added a commit that references this issue on May 13, 2026This issue will close once commit efe3761 is merged into the 'master' branch.efe3761
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|