Fix bug when adding a Satochip key directly after importing a BIP39 seed#6907
Merged
cakesoft-vaibhav merged 3 commits intoKeeperCommunity:sprintfrom Mar 30, 2026
Merged
Conversation
This error happens when adding a Satochip signer directly after importing a BIP39 seed via the 'Setup options'
Error message: ```SetupSatochip.tsx:226 Warning: TypeError: Cannot read property 'n' of undefined```
Root cause: ImportSatochipSeed used CommonActions.navigate("EnterSeedScreen"),
which pops back to an existing EnterSeedScreen already below AddSigningDevice
in the stack, ejecting AddSigningDevice and SetupSatochip. When
SatochipSeedImportModal later navigated back to SatochipAction it created a
fresh instance with no original params, so scheme.n was undefined → crash.
Additionally, setupSatochipParams was passed into SatochipSeedImportModal but
never forwarded to SatochipAction on close, losing isMultisig/accountNumber/
signer context needed for the subsequent NFC signing step.
Changes:
- ImportSatochipSeed: replace CommonActions.navigate → StackActions.push for
EnterSeedScreen so a new instance is always pushed, preserving AddSigningDevice
in the stack
- SatochipSeedImportModal: extract setupSatochipParams from route.params and
spread it into the SatochipAction return navigation so original SetupSatochip
params are fully restored after seed import
When card is not setup, authenticity cannot be evaluated.
ben-kaufman
approved these changes
Mar 29, 2026
cakesoft-vaibhav
merged commit f43fa9a
into
KeeperCommunity:sprint
1 of 2 checks passed
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
3 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.
During testing, we noticed a bug when adding a Satochip key directly after importing a BIP39 seed via the 'Setup options'.
Console error message:
SetupSatochip.tsx:226 Warning: TypeError: Cannot read property 'n' of undefinedRoot cause: ImportSatochipSeed used CommonActions.navigate("EnterSeedScreen"),
which pops back to an existing EnterSeedScreen already below AddSigningDevice
in the stack, ejecting AddSigningDevice and SetupSatochip. When
SatochipSeedImportModal later navigated back to SatochipAction it created a
fresh instance with no original params, so scheme.n was undefined → crash.
Additionally, setupSatochipParams was passed into SatochipSeedImportModal but
never forwarded to SatochipAction on close, losing isMultisig/accountNumber/
signer context needed for the subsequent NFC signing step.
Changes:
EnterSeedScreen so a new instance is always pushed, preserving AddSigningDevice
in the stack
spread it into the SatochipAction return navigation so original SetupSatochip
params are fully restored after seed import
This PR has been tested and patches the issue.