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

"Reset Application" does not remove local db anymore / if not logged in #2060

Closed
sleidig opened this issue Nov 3, 2023 · 4 comments · Fixed by #2090
Closed

"Reset Application" does not remove local db anymore / if not logged in #2060

sleidig opened this issue Nov 3, 2023 · 4 comments · Fixed by #2090
Labels
released on @master managed by CI (semantic-release) released managed by CI (semantic-release) Type: Bug

Comments

@sleidig
Copy link
Member

sleidig commented Nov 3, 2023

Describe the bug
The Support Screen button to "Reset Application" does not work anymore. The browser indexeddb remains unchanged when visiting that screen without being logged in. Therefore it cannot be used to recover from issues where the user can't login anymore.

To Reproduce
Steps to reproduce the behavior:

  1. Open an instance in "synced" mode (with persisted local db), e.g. https://demo3.aam-digital.com
  2. Login, sync, ...
  3. Logout
  4. Navigate to the support page through the browser URL (e.g. https://demo3.aam-digital.com/support)
  5. Click "Reset Application"
  6. Checking in the browser console, you see that the indexeddbs are still filled

Expected behavior
Should remove all indexeddbs, resetting the app overall for any user on this device.

@TheSlimvReal
Copy link
Collaborator

This is because the username is needed in order to know which db to reset. An alternative approach would be to delete all indexed-dbs

@sleidig
Copy link
Member Author

sleidig commented Nov 19, 2023

In my opinion we should delete all indexedDBs (at least when not logged in)

@aam-digital-ci
Copy link
Collaborator

🎉 This issue has been resolved in version 3.26.0-master.25 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@aam-digital-ci aam-digital-ci added the released on @master managed by CI (semantic-release) label Nov 21, 2023
@aam-digital-ci
Copy link
Collaborator

🎉 This issue has been resolved in version 3.26.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@aam-digital-ci aam-digital-ci added the released managed by CI (semantic-release) label Nov 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released on @master managed by CI (semantic-release) released managed by CI (semantic-release) Type: Bug
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants