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
I encountered a problem while using the WalletConnect web3inbox application where I hit the 5MB limit of local storage.
Steps to Reproduce:
Use the application for a prolonged period, interacting with various features (e.g., sending and receiving messages).
Monitor the local storage usage in the browser's developer tools.
Expected Behavior:
I expected the application to manage local storage efficiently, either by pruning older messages or notifying me before hitting the storage limit.
Actual Behavior:
Upon reaching the storage limit, I received an error message indicating that I could not save any more data. This affected my ability to send or receive new messages, causing interruptions in usage.
Additional Information:
Environment: [Specify the browser and version, e.g., Chrome v115.0.0, Windows 10]
Link to application: [Provide a link to the web3inbox application if applicable]
Can we investigate whether there’s a mechanism in place to automatically prune older messages or if this is a bug in the NotifyClient?
The text was updated successfully, but these errors were encountered:
I encountered a problem while using the WalletConnect web3inbox application where I hit the 5MB limit of local storage.
Steps to Reproduce:
Expected Behavior:
I expected the application to manage local storage efficiently, either by pruning older messages or notifying me before hitting the storage limit.
Actual Behavior:
Upon reaching the storage limit, I received an error message indicating that I could not save any more data. This affected my ability to send or receive new messages, causing interruptions in usage.
Additional Information:
Can we investigate whether there’s a mechanism in place to automatically prune older messages or if this is a bug in the NotifyClient?
The text was updated successfully, but these errors were encountered: