Forum Discussion

DzungVu's avatar
DzungVu
Copper Contributor
Oct 21, 2024

Edge 130.0.2849.46 (Official build) (64-bit) Broke Extension(s) - Ublock Origin in this case.

Hello,
I know very well that Edge is also moving to MV3.
But, there isn't any announcement about complete removal of MV2 yet.


Since Edge updated to v130, it broke popular extension like Ublock Origin, for many people.
We've reported the issue to extension devs, it but seems that while there are many people who are affected, there still be many that have extension working fine as expected.
https://github.com/uBlockOrigin/uBlock-issues/issues/3419
Many people've reported this issue not only on github, but also on reddit as well.


The extension was working fine before v130, so we suspect that the cause is Edge update itself.
- Issue: The extension loads but cannot run, and its dashboard page cannot load, is completely empty.
Turn on/off does not work. Removing/Reinstalling from MSEdge Store also does not work.
The only "workaround" for this is setting up a completely new blank local profile, but that will cost all the synced settings and extensions data.


Please help us looking into this issue,
Thank you.
---------------------------------
Browser: Edge 130.0.2849.46 (Official build) (64-bit)
Extension: Ublock Origin v1.60.0
Extension source: MSEdge Store
System: Windows 10 22H2 19045.5011 (I don't think system info matters because there're people who're on Win11 and have this issue as well)

BUG
BUG Report
Bug Reporting
Microsoft Edge bug
  • ScottCIS's avatar
    ScottCIS
    Brass Contributor
    Oct 23, 2024
    DzungVu wrote:

    The only "workaround" for this is setting up a completely new blank local profile, but that will cost all the synced settings and extensions data.

    Actually, once you create a new profile, the extension starts working for existing profiles. You can then just delete the new profile. I've had to do this for 2 users so far.

  • NateCyber's avatar
    NateCyber
    Copper Contributor
    Oct 23, 2024
    More context: UBO developer Gorhill says this is affecting other ad-blockers as well, not just UBO.
  • karl1460's avatar
    karl1460
    Copper Contributor
    Oct 22, 2024

    Hello! Browser extension developer (of a different extension, not Ublock Origin) here - we are also seeing very strange behavior on Windows, with Edge version 130.0.2849.46 (Official build) (64-bit) on the stable channel.

    We've tracked the problem down to `browser.storage.managed.get` and `chrome.storage.managed.get` - it seems that function has simply broken, or is behaving very incorrectly, on this version of Edge. When we run the following Javascript from the Service Worker JS Dev Console...

    ```
    console.log(`before get`);
    const results = await browser.storage.managed.get('key');
    console.log(`after get results`, results);
    ```

    ...the second console.log statement simply does not run. It's like the Edge browser itself stops evaluating JavaScript.

    Even stranger, we've tried 130.0.2849.46 (Official build) (64-bit) beta channel, and surprisingly, that DOES work fine! We did that based on feedback in https://github.com/uBlockOrigin/uBlock-issues/issues/3419

    So it seems like something is broken with the stable channel version of this, but it works fine in the beta channel.

    We're hoping for a fix to come very quickly, because this is impacting a huge number of our users. And we suspect the same thing is happening for uBlockOrigin, too.

    It looks like there is a bug reported here, too: https://github.com/microsoft/MicrosoftEdge-Extensions/issues/179

    Thanks,
    Karl

Resources