Skip to content

Signed Mv-2 Release: 0.2237

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 05 Apr 22:45
· 293 commits to main since this release
f8fbdd1

Why am I in development mode?

The Mv2 version of the extension considers injection scripts being packed in as development mode.

Why is the injection script packed?

For security. It was why we were removed from the Firefox addon store.

Why is the button stuck at “downloading bypass definitions…”?

This issue has been fixed (read removed entirely) on the Mv3 branch, so there’s no point fixing it here.

Till when should I use this version? Will it update automatically or will I have to do something?

This is a bit of an awkward time as Mv2 is about to be deprecated but the Mv3 version is not completely ready and lacking some bypasses. When the Mv3 version is ready we’ll announce it on our Discord server and ship it to browser stores. Then you will have to manually uninstall the Mv2 version and install the Mv3 version. We recommend joining our Discord server to stay updated.

What is Mv2 and Mv3?

Manifest V2 (MV2) and Manifest V3 (MV3) are different versions of the manifest file that defines how a browser extension should behave (read more). Universal bypass was built on Mv2 and we had to re-write pretty much everything to make it comply with Mv3. This was a big change so Mv2 bypasses don't work on the Mv3 version. We're are in the process of converting them but it is a slow process. How you can help.