-
-
Notifications
You must be signed in to change notification settings - Fork 28
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.
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
Any updated to MV3 planned? #28
Comments
@cryptoKevinL Yes, we're currently working on upgrading the manifest version to v3 for Chrome. |
Cool! thanks so much @kevinghim - any ETA on that? 1 month away, 6 months away? Really struggling with the use of MM in my MV3 Chrome Extension - just declaring the provider kills all my alarms that normally run in the background just fine when the extension is closed. There must be some error downstream I can't find thats not being bubbled up to the main debug windows |
@cryptoKevinL no specific ETA, but we're planning on migrating to MV3 well before the Jan '23 deadline |
Hey @kevinghim just bumping this up once again. Any approx ETAs for V3? Would you guys like some support? |
Should this issue be associated with https://github.com/MetaMask/metamask-extension/milestone/69 ? |
Hi any updates on the release? |
The deadline has passed. |
Hi, are there any examples of this package used in Manifest V3 or are they any plans to upgrade this to MV3? I'm struggling to use Metamask in my MV3 application without the provider breaking my alarms, and general things used in the new MV3 background worker. Thanks!
The text was updated successfully, but these errors were encountered: