Opera 109.0.5097.24 beta update

[adioni-home]

adioni-home last edited by

Opera 109.x keeps preventing the lastpass extension (tried both the version from the opera extensions site and the version from the chrome store) from being loaded as it says it is damaged and in need of repair. The repair button does nothing. Reverting to prior opera versions the extension loads fine with the browser.

[siemfan]

siemfan last edited by

Great, now all my extensions from Chrome Store is "corrupted". Rolling back to previous Opera version doesn't help.

[wooky1]

wooky1 last edited by

Same problem. Extensions from Chrome Store are "corrupted"

[modemjunkie]

modemjunkie last edited by

Same here. All of my social sharing (extensions are disabled because they are deemed corrupted by Opera. (I share most frequently to Twitter pr facebook, The same is true with a couple of "Reader" apps, like clearly. Downloading alternative extensions from either the Opera or Chrome store, doesn't help. New extensions a reported immediately as corrupted when I install them. Very frustrating. Using Opera One(version: 109.0.5097.24)

[eliotcougar]

eliotcougar last edited by

After the update all extensions from Chrome Web Store stopped working... They all report as being corrupted... Any new extension immediately says it's corrupted immediately after installation...

[eliotcougar]

eliotcougar @eliotcougar last edited by

@eliotcougar: Looks like the problem is related to the extensions being Manifest v2 type... I've managed to force the extensions into a working state by switching to the Developer Mode, then Load Unpacked, and pointing it to the folder where Opera stores the extension in question: C:\Users[username]\AppData\Roaming\Opera Software\Opera Next\Default\Extensions
You need to navigate inside the folder of the extension where its manifest.json is located...

[eliotcougar]

eliotcougar @eliotcougar last edited by

@eliotcougar: Hmmm... My previous assumption is probably incorrect... One of the failed extension is Manifest version 3... Then, maybe, the problem is with calculating hashes when an extension is installed and/or verified??? Because when I try to install any new extension from the Chrome Web Store, the extension's _metadata\computed_hashes.json and _metadata\verified_contents.json files are not created as they should…

[hartkor]

hartkor last edited by

Same thing. All extensions installed from chromstore are disabled with the same error "This extension may have been corrupted.".

[burnout426]

burnout426 Volunteer last edited by burnout426

The extension issue is a known issue and looks to be the same as the extension corruption issue that happened in 108 not too long ago.. It looks like this build is missing a patch/fix for that issue for some reason.

[modemjunkie]

modemjunkie @burnout426 last edited by

@burnout426 Thanks. In the meantime I have switched to Opera One(version: 108.0.5067.29) Stable) which I had also installed on my machine.

[hassan912]

hassan912 last edited by

I had the same problem.

[acerswap]

acerswap last edited by

Same problem for me with the extensions.

Also, an extension I loaded from outside Chrome Store (Bypass paywalls clean) is failing too.

[hartkor]

hartkor last edited by

The beta has been updated to build 109.0.5097.36, but this has no effect on the extensions working (or rather not working).

[hartkor]

hartkor @hartkor last edited by

@hartkor: I miss my extensions, and I'm waiting for the new beta version, in which hopefully everything will work as before.