Joe Campo

Hey there @victorgarciaesgi, first thanks for building & maintaining this! I'm dealing with something I think that may be similar to this issue so I didn't open another. Since 3.1.4...

@victorgarciaesgi This fixes it! Thanks so much to tackling this so quickly.

@jtomlinson @stevepop Gents, I've been debugging this as well. I've noted that I don't have the same problem using us-2 instead of us-1. Curious if you both have the same...

Interesting, since I've switched to us-2 I haven't had the issue pop up at all.

> > @jtomlinson @stevepop Gents, I've been debugging this as well. I've noted that I don't have the same problem using us-2 instead of us-1. Curious if you both have...

@baltagih2 I've run into the same issue, for me it is using react navigation tabs and using the `bottomOffset` prop: https://github.com/FaridSafi/react-native-gifted-chat/pull/2353#issuecomment-1477206396

@baltagih2 I'm guessing you're also using React Navigation with tabs and were specifying the `bottomOffset` prop? If so, there isn't a workaround yet, but I submitted a PR to fix:...

@baltagih2 How big is the gap? If small, even when not using bottomOffset it would set it to `1` when the keyboard was shown even if the prop was not...

@baltagih2 and I'm assuming no gap when the keyboard is closed? Anyways, I'd wait for the PR to be merged and see if that fixes this. I'm not a maintainer...

@clue Sorry for the ping & thank you for all your hard work! :) I noticed that the 4.0 version tagged on Github for `react\async` does not include the new...