-
Notifications
You must be signed in to change notification settings - Fork 128
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
Chrome extension login failed on PubMed #1462
Comments
Hello @courtneythaxton, I'm afraid this is a known issue that appeared recently when logging into the client from a PubMed page. The workaround is to open a tab at a different site, log in to Hypothesis there, and then go to PubMed and annotate. |
A note for Hypothesis developers, the underlying issue is hypothesis/client#5769. There is also an internal issue at https://github.com/hypothesis/support/issues/85. |
Another workaround is to use https://via.hypothes.is to annotate affected pages instead of the browser extension. |
@robertknight Thank you so much for the update. I had a couple weeks back logged in at the hypothes.is webpage and that seemed to work, but it stopped this week. So I took your advice and tried a different page than PubMed and Hypothes.is, I choose ClinVar, and was able to log into my groups and authorize. Thanks for the work around! Best, |
I can no longer login with the Google Chrome Extension. When I am on a web article, the extension opens, to show the "Public" group; however, when I go to login to my account I receive an error (see image below). It seems to be an authorization error, as a separate window opens to authorize but never completes.
I can sign in if at the hypothes.is webpage, but not through the extension, which prevents me from using the tool
I am using a MacBook Pro (2021), MACOS Monterey v12.1.
Google Chrome Info: Chrome is up to date Version 121.0.6167.160 (Official Build) (arm64)
This is negatively affecting my work, as I depend on this tool for completion of assignments.
The text was updated successfully, but these errors were encountered: