-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not get oauth token, currently only support Chrome #138
Comments
as it said, it only supports Chrome since the extension will use the Chrome login user. |
Hi @leonhartX , I have the same issue when using Chrome. Google Chrome is up to date, Version 88.0.4324.190 (Official Build) (64-bit). I've checked that Script API is enabled and checked that the API scope includes gist and all repo selections. I've also checked that the options menu shows that I am logged in. (Which is does.) Is there any additional information that I can provide that would help to debug this issue? |
umm, can you provide something in the console log when the error happened? |
I've had a look in the console but I can't see anything that seems to be related. This is what I've got. If you would like me to get more information on any particular warning / error, just let me know.
|
Is this thread still alive? I'm seeing the same error message "[github assistant] can not get oauth token, currently only support Chrome", and in the console I also have that same warning as dj4g11e32: DevTools failed to load source map: Could not load content for https://www.gstatic.com/monaco_editor/min-maps/vs/base/worker/workerMain.js.map: Fetch through target failed: Target not supported; Fallback: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE I'm using Chrome 9.10 on macOS 10.14.6. |
Same error on macOS version 103.0.5060.114 (Official Build) (x86_64). |
I had this problem pop up suddenly after I had been using it on Windows 10 for awhile. Uninstalling Chrome (with removing Data) and reinstalling Chrome, then re-adding the extension fixed the issue for me. Although I suspect uninstalling the extension, removing all of it's data from the file system, and reinstalling it would have worked as well. |
Installed this app today and seeing this issue. Tried creating a new token bunch of times but nothing works. Is this app obsolete and does not work anymore? |
I'm not sure how to solve your issue, but I've used this app as recently as last week so the app does still work. |
@wencl-william Thanks for your response. If you log back in using github, do you see the Google popup saying |
@srujanb I get the part of that popup that asks for what Google account to use and (when using an account for the first time) the screen that then asks for permissions for the app. I don't get the screen saying "Google hasn't verified this product" |
@wencl-william weird, I don't see any popup like that (not even the one you mentioned). As soon as I login with github I get a log Alternatively, I tried Github/bitbucket/gitlab and a Chromium as well but nothing works. Chrome version: Version 120.0.6099.129 (Official Build) (arm64) |
In Chromium I got such error after auth in Gitlab with API token (login with password also do not work). Why? What I can do with it?
Cromium version 88.0.4324.96 (Developer Build) Fedora Project (64-bit).
The text was updated successfully, but these errors were encountered: