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.

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

"sql: database is closed" toast appears every 5 seconds after Profile log out #22206

Open
mariia-skrypnyk opened this issue Feb 27, 2025 · 0 comments · May be fixed by #22212
Open

"sql: database is closed" toast appears every 5 seconds after Profile log out #22206

mariia-skrypnyk opened this issue Feb 27, 2025 · 0 comments · May be fixed by #22212
Assignees
Labels
wallet: swap wallet-core Issues for mobile wallet team
Milestone

Comments

@mariia-skrypnyk
Copy link

Bug Report

issue was firstly detected and reported here #21999 (comment) but it seems not to be fixed

Precondition:

  1. The app should remain in the background for approximately 1 hour or more.
  2. 1–2 profiles with assets should be added to the app.

Reproduction

  1. Resume the app from the background
  2. Login to the Profile 1
  3. Go to Wallet -> Swap
  4. Choose networks and enter amount (no matter what data you choose)
  5. Tap on max slippage
  6. Do some changes there
  7. Leave Swap and do a log out

*in case you have Profile 2 you can repeat all these steps and you'll see an error
** all my steps consistently lead to the 10/10 issue, but I am not sure if they are unique or if the issue can be triggered by other steps as well. This is just what worked for me.

Actual behavior

"sql: database is closed" toast appears every 5 seconds on the Profiles screen.

Image

logs:

sql_error_logs.zip

Expected behavior

No error.

Additional Information

  • Status version: release build
  • Operating System: Android, iOS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wallet: swap wallet-core Issues for mobile wallet team
Projects
Status: Code Review
Development

Successfully merging a pull request may close this issue.

3 participants