fix: preserve Android bond failure reasons - #25
Closed
wabicai wants to merge 1 commit into
Closed
Conversation
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
1 participant
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.
Android bonding failures only exposed the old and new bond states, so the SDK could not distinguish authentication timeouts, local cancellation, remote rejection, or other failures. Forward the optional Android unbond reason in
bondState.reasonand release0.1.7.Validation: package build and TypeScript checks passed; changed-file lint passed; the generated npm tarball contains the Kotlin change and declaration. An Android device build with the matching SDK change was installed and the user confirmed normal logs.