fix(tonconnect): exclude undefined stateInit from proof response#548
Merged
nvasilchuk merged 1 commit intomainfrom Feb 17, 2026
Merged
fix(tonconnect): exclude undefined stateInit from proof response#548nvasilchuk merged 1 commit intomainfrom
nvasilchuk merged 1 commit intomainfrom
Conversation
Successful WEB deployment 🚀🚀🚀Well done! |
|
lgtm |
nvasilchuk
approved these changes
Feb 10, 2026
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.
Summary
stateInit: undefinedappearing in TonConnect proof response in Firefox extensionstateInitonly when definedProblem
Firefox preserves
undefinedvalues duringpostMessageserialization, causing TonConnect SDK to seestateInit: undefinedinstead of the field being absent.Solution
Use spread operator to conditionally include
stateInitonly when it's defined.Fixes PRO-404