Merged
Conversation
add script for paste board sync due to ios simulator bug
illuzen
approved these changes
Apr 3, 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
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.
Fix send screen responsiveness (closes #431, closes #432)
Summary
Details
The performance improvements are straightforward, just rearranged fetch estimated balance etc
The biggest issue was the keyboard. The send screen shows 2 text fields, one with an alphanumeric keyboard, the other with a decimal number pad.
The OS will do a little keyboard up/down animation when it's switching, but the component would react and move up and down too, very disturbing on this screen.
Turns out this is non trivial to fix on a bottom sheet, which also needs to handle a hardware keyboard (no screen keyboard), switching between hardware keyboard and on-screen keyboard, and different keyboard heights (potentially although not on iOS)
In part this is because the bottom sheet component and scroll views have some automatic keyboard detection built in. Fixed now though.