Wappalyzer: Corrupted in Edge Chromium

Created on 5 Feb 2020  路  13Comments  路  Source: AliasIO/wappalyzer

Platform
Which platform does the bug apply to?

  • Microsoft Edge Chromium Extension
  • MacOS Catalina and Microsoft Windows

Describe the bug
screenshot

Additional context
I tried to repair, but it still happens.

Bug

Most helpful comment

Microsoft has assured me they fixed the issue on their end. A new version is waiting approval now, as soon as that becomes available this should be resolved.

All 13 comments

I'm getting the same exact error.

I agree, I am also having issues with wappalyzer in the Edge Chromium browser as well.

For me installing the chrome web store version fixes it atm

Exact same error here. It shows the error messages sometimes though. It should be fixed asap as Edge seems to be an excellent alternative to Chrome.

The latest version was just approved, please let me know if that fixes it.

@AliasIO - nope, still breaks.

Same, still break for me.

Currently also getting this issue. I can repair it and it re-enables the plugin. Once I reload a website and click on the plugin it disappears from the toolbar and it shows the same error message again in the extensions overview.

Just saw that the plugin got upgraded to 5.9.30 and got really excited since it was working while I stayed on Google. I went to YouTube and it immediately crashed again and shows the error message in the extensions overview.

So I repaired it and tried not going to YouTube but other websites and it seems to work. But as soon as I go back to YouTube it crashes again. Seems like some sort of technology that is running on YouTube causes Wappalyzer to crash.

I'm unsure how to debug this as the console crashes along with the extension. I noticed on some sites it works fine (e.g. https://example.com), on some it crashes when the popup opens (https://www.wappalyzer.com) and on others it crashes immediately (https://www.youtube.com).

It only happens when the extension is installed from the Edge store. No issues installing it locally or from the Chrome store.

After updating to 5.9.30, It's still broken.

Microsoft has assured me they fixed the issue on their end. A new version is waiting approval now, as soon as that becomes available this should be resolved.

This has now been resolved.

Was this page helpful?
0 / 5 - 0 ratings