Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Chrome alarm is not identifying which alarm is getting triggered correctly. #16359

Closed
NiranjanaBinoy opened this issue Nov 2, 2022 · 0 comments · Fixed by #16360
Closed

Chrome alarm is not identifying which alarm is getting triggered correctly. #16359

NiranjanaBinoy opened this issue Nov 2, 2022 · 0 comments · Fixed by #16360
Assignees
@NiranjanaBinoy
Labels
MV3 PR - P1 identifies PRs deemed priority for Extension team

Comments

@NiranjanaBinoy
Copy link
Contributor

We have two locations where we are using chrome alarms at the moment; one goes off every 1 minute, and the other goes off based on a user-defined interval. Both the addlisteners catches an alarm when it is triggered, and currently, we are not correctly identifying which alarm is getting triggered at that time, resulting in both alarms getting executed every minute.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NiranjanaBinoy NiranjanaBinoy

Labels
MV3 PR - P1 identifies PRs deemed priority for Extension team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: To differentiate between which chrome alarm is triggered MetaMask/metamask-extension
1 participant
@NiranjanaBinoy