metamask-mobile
metamask-mobile copied to clipboard
[Sentry] Error: User interaction is not allowed.
Sentry Issue: METAMASK-MOBILE-2BVZ
Error: User interaction is not allowed.
at r (ses.cjs:7575:17)
at backupVault (app/core/BackupVault/backupVault.ts:41:32)
at <global> (app/core/BackupVault/backupVault.ts:37:34)
at controllerMessenger.subscribe$argument_1 (app/core/Engine.ts:954:9)
at key (app/core/LockManagerService/index.ts:27:33)
...
(45 additional frame(s) were not displayed)
Comment: Error seems to happen when backing up the vault.
Sentry Issue: METAMASK-MOBILE-2BWR
Sentry Issue: METAMASK-MOBILE-2BYB
Sentry Issue: METAMASK-MOBILE-2C1X
Sentry Issue: METAMASK-MOBILE-2C1W
Sentry Issue: METAMASK-MOBILE-2CHF
Sentry Issue: METAMASK-MOBILE-2C0H
Sentry Issue: METAMASK-MOBILE-2C0J
Sentry Issue: METAMASK-MOBILE-2CHA
Sentry Issue: METAMASK-MOBILE-2E6K
Sentry Issue: METAMASK-MOBILE-2E6M
Sentry Issue: METAMASK-MOBILE-2ENW
This issue seems to happen when Secure Store is accessed when the app is locked.
The breadcrumb of this error on Sentry shows a navigation to the lockscreen just before this error.
I feel it could be interesting to investigate a sync issue between the lock and unlock functions as the lock is not awaiting and then could miss a state or override one. See https://github.com/MetaMask/metamask-mobile/blob/main/app/components/Views/LockScreen/index.js#L128-L128
Sentry Issue: METAMASK-MOBILE-263W
This error is associated with attempting access to the keychain on iOS when it is not available. https://github.com/oblador/react-native-keychain/issues/404
Do you think this could be because of the app lifecycle as we can see navigation to the lockScreen just before the error? So checking the app lifecycle state before trying to access the keychain could help?
Sentry Issue: METAMASK-MOBILE-2G7V
Sentry Issue: METAMASK-MOBILE-2GAY
Sentry Issue: METAMASK-MOBILE-2GH3
Sentry Issue: METAMASK-MOBILE-2GDN
Sentry Issue: METAMASK-MOBILE-2GJJ
This issue has been automatically marked as stale because it has not had recent activity in the last 90 days. It will be closed in 7 days. Thank you for your contributions.
This issue was closed because there has been no follow activity in 7 days. If you feel this was closed in error please provide evidence on the current production app in a new issue or comment in the existing issue to a maintainer. Thank you for your contributions.