Skip to content

fix: await onVaultUpdate to prevent save interruption on popup close#4

Merged
0xneves merged 1 commit intorefactor/visualfrom
develop
Feb 6, 2026
Merged

fix: await onVaultUpdate to prevent save interruption on popup close#4
0xneves merged 1 commit intorefactor/visualfrom
develop

Conversation

@0xneves
Copy link
Owner

@0xneves 0xneves commented Feb 6, 2026

The bug was that contacts (and potentially groups/identities) were being lost when the extension popup was closed quickly after adding them.

Root cause: onVaultUpdate() was not awaited, so the UI would show success and allow the popup to close before saveVault() completed. When the popup closes, its JS context is destroyed, potentially interrupting the save.

Fixed all occurrences in:

  • DashboardScreen.tsx (6 places)
  • ConnectFlowScreen.tsx (3 places)
  • OnboardingScreen.tsx (1 place)

Now the UI waits for the save to complete before closing modals/showing success.

The bug was that contacts (and potentially groups/identities) were being lost
when the extension popup was closed quickly after adding them.

Root cause: onVaultUpdate() was not awaited, so the UI would show success
and allow the popup to close before saveVault() completed. When the popup
closes, its JS context is destroyed, potentially interrupting the save.

Fixed all occurrences in:
- DashboardScreen.tsx (6 places)
- ConnectFlowScreen.tsx (3 places)
- OnboardingScreen.tsx (1 place)

Now the UI waits for the save to complete before closing modals/showing success.
@0xneves 0xneves merged commit 72fd13d into refactor/visual Feb 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant