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.

Sign up for GitHub

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

Jump to bottom

Errors: 'Could not establish connection' and 'Extension context invalidated' #66

Open
max-ostapenko opened this issue Sep 23, 2024 · 1 comment · May be fixed by #65
Open

Errors: 'Could not establish connection' and 'Extension context invalidated' #66

max-ostapenko opened this issue Sep 23, 2024 · 1 comment · May be fixed by #65

Comments

@max-ostapenko
Copy link

Platform
Which platform does the bug apply to?

  • WebExtension (Google Chrome)

Describe the bug
While using the local extension version to test the new rules I often have the errors:

  • Uncaught (in promise) Error: Extension context invalidated.
  • Error: Could not establish connection. Receiving end does not exist.

I'm not sure if due to these errors there are issues with the technologies being detected and displayed.

To Reproduce
Approximate steps:
1 Go to a tested website 1
2. Update the rules
3. Hit Refresh in chrome://extensions/
4. Go to a tested website 2 and refresh the page
5. Check the errors

Expected behavior

  • handle these cases in extension communication, or make errors of tech detection more obvious
@tunetheweb
Copy link
Member

We don't own this extension. Wappalyzer does. This is just a clone of their repo as off when they went closed-source. As they are closed-source now I don't think you can contribute any fixes.

@max-ostapenko max-ostapenko linked a pull request Sep 23, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Chrome extension code cleanup HTTPArchive/wappalyzer
2 participants
@max-ostapenko @tunetheweb