Fix/issue 1 wallet state navigation - #149
Merged
N-thnI merged 2 commits intoAug 3, 2026
Merged
Conversation
N-thnI
added a commit
that referenced
this pull request
Aug 4, 2026
PR #149's squash-merge onto main independently-added-but-differently- named MockSocket/MockedSocket mock types in both files without conflicting line-for-line, so git's merge silently concatenated both versions instead of flagging a conflict. The result was invalid TypeScript (duplicate type/function/jest.mock declarations), breaking typecheck on main. Keeps the single MockedSocket version, matching what was on main before the merge.
N-thnI
added a commit
that referenced
this pull request
Aug 4, 2026
PR #149's squash-merge onto main independently-added-but-differently- named MockSocket/MockedSocket mock types in both files without conflicting line-for-line, so git's merge silently concatenated both versions instead of flagging a conflict. The result was invalid TypeScript (duplicate type/function/jest.mock declarations), breaking typecheck on main. Keeps the single MockedSocket version, matching what was on main before the merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
This PR addresses a bug where the Guardian’s connected Freighter wallet address is lost when navigating from the home page to deeper dashboard views. The WalletContext was re-initializing, causing unexpected disconnect loops.
Changes:
Persist connected wallet address in window.localStorage (or secure session cache) after successful association.
Read cached address during initial useEffect setup in WalletContext.tsx.
Add safe handling for disconnect events by clearing cached variables across state systems.
Acceptance Criteria:
Connected address remains stable across page navigation.
Disconnect events properly clear cached state without triggering loops.
closes #1