Closed lastmeta closed 2 years ago
first 2 seem fine.
4 is broken because, I think, our image. maybe something with it being multicolored or the stem being near the same color as the primary color idk. but when I removed the image it worked fine.
5 - will test with updated qr without image overlay
concerning 7 we don't really choose the keyboard they use, but the reason it isn't swiping down, I think, is because the thing they are trying to swipe is usually a column of list view (the thing behind the keyboard). So for now I think the best solution is to make sure that's always wrapped in a guesture detector which will unfocus the scope and therefore drop the keyboard. that way they can tap anywhere on the screen and it'll dismiss the keyboard.
We've talked about altering the way we use the keyboard altogether - having it come up in front of eveything without interacting with the contents at all, and we'd manage that interaction, when we do that this problem will likely be fixed more generally because we wont have the need to make things scrollable because the screen will not change in size which is what the keyboard essentially does right now... causing every page to basically need to be scrollable.
as for 9 I couldn't see any issue except the paste button shows up under the app bar which is really annoying, still working on it I think we have a different ticket for that specifically
as for 5 it seems it only has this problem if the user doesn't "complete" the action. So added a refresh even if the user goes to the next field by clicking it rather than pressing enter.
Describe The Bug
on ios import flow -
scanning and sending -
snackbar -
keyboard issue -
suggestion -
import screen -