Skip to content
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

"Error authenticating account" in editor #1316

Closed
fregante opened this issue Sep 14, 2021 · 1 comment
Closed

"Error authenticating account" in editor #1316

fregante opened this issue Sep 14, 2021 · 1 comment

Comments

@fregante
Copy link
Collaborator

fregante commented Sep 14, 2021

I'm not sure if this is a DX issue or if it happens in the wild too. Classifying it as DX for now.


Screen.Recording.2.mov

How to replicate

  1. Build the extension locally (npm run watch)
  2. Let web-ext reload the background page (web-ext run)
  3. Open the dev tools on any website

Possible reasons

  • The background page might have completely failed to load (due to a a build error or runtime/init error for example)
    • open the background page’s console to double-check
  • The extension might not have reloaded fully (e.g. the background page loaded by Chrome did not execute any code 🤷‍♂️ )
    • Reload the extension manually by clicking the reload button in chrome://extensions
  • The token might be wrong or provided to the wrong SERVICE_URL
    • Clear token in PixieBrix’ options and login again

Suggested solution

  • Debug the auto reloading and report back to web-ext
  • Show a better message to the user

Possibly related

cc @MMirandi because you mentioned the issue on Slack

@fregante
Copy link
Collaborator Author

I haven't seen this in a while

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant