MetaMask / MetaMask/extension-provider

Using Alarms and extension-provider not working

Open
#27 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
73
Forks
29
PR merge metrics
No merged PRs in 30d

Description

In manifest V3, I am using Alarms, just simply incrementing a counter once a minute. When I add this extension, and declare it - the alarms never fire. Is there something in the init code that is declaring its own alarms or some issues with V2 vs V3?

let provider = createMetaMaskProvider() (just this cases alarms not to fire)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported Manifest V3 case with a one-minute counter alarm, first without and then with createMetaMaskProvider(). Check whether the provider initialization changes alarm behavior or conflicts with Manifest V2/V3 assumptions; done means the alarm fires reliably with the provider enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.