You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ERROR {"context": "client"} Missing or invalid. Record was recently deleted - proposal: 1746767498888928
We recently migrated from WalletConnect to Reown, and encountered a regression in session handling behavior.
At first, we thought it was an issue on our side, but we confirmed that the same problem also occurs in Reown’s official wallets/rn_cli_wallet implementation.
Even though the session proposal is successfully approved, we observe that a proposal_expire event is triggered 5 minutes later.
This behavior did not occur in @walletconnect/web3wallet: 1.12.3, but has been consistently observed in all versions of Reown
Expected Behavior
Once a session proposal is approved and the session is connected, the proposal should not expire.
Actual Behavior
After successful approval and connection, the proposal_expire event still fires after 5 minutes.
Uh oh!
There was an error while loading. Please reload this page.
Description
We recently migrated from WalletConnect to Reown, and encountered a regression in session handling behavior.
At first, we thought it was an issue on our side, but we confirmed that the same problem also occurs in Reown’s official wallets/rn_cli_wallet implementation.
Even though the session proposal is successfully approved, we observe that a
proposal_expire
event is triggered 5 minutes later.This behavior did not occur in
@walletconnect/web3wallet: 1.12.3
, but has been consistently observed in all versions of ReownExpected Behavior
Once a session proposal is approved and the session is connected, the proposal should not expire.
Actual Behavior
After successful approval and connection, the
proposal_expire
event still fires after 5 minutes.Log
Issue Environment
Output of
npx react-native info
Steps to reproduce
proposal_expire
event is triggered, despite the session already being approved and connectedThe text was updated successfully, but these errors were encountered: