chore: bump bitbox_flutter to v0.0.8#714
Merged
Merged
Conversation
v0.0.8 contains the Android pairing-code fix (#26): initBitBox now runs off the serial MethodChannel task queue, so the BitBox channel hash (pairing code) appears in the app and on the device simultaneously instead of only after on-device confirmation. iOS was already unaffected.
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.
Summary
Bumps the
bitbox_flutterdependency fromv0.0.7tov0.0.8.v0.0.8contains the Android pairing-code fix (DFXswiss/bitbox_flutter#26):initBitBoxnow runs off the serial MethodChannel task queue, so the BitBox pairing code (channel hash) appears in the app and on the device simultaneously, instead of only after confirming on the device. iOS was already unaffected.Test plan
flutter pub getresolvesbitbox_flutter v0.0.8