baltagih2

Is there any solution other than guessing a number that could work? Something like "as soon as state is ready, render UI" instead of waiting for a timeout?

Hello all, this was never merged and the renderUsername prop still doesn't work

For anyone still running into this problem, the following worked for me (based on the commit from @julienc91 above): `npm i jsdom` `npm i --save-dev @types/jsdom` ``` import { JSDOM...

Any workaround @joecampo in the meantime?

@joecampo I'm actually not using the `bottomOffset` prop and not using tabs. Regular Stack React Navigation, was using `wrapInSafeArea={false}` and handling everything myself but the prop was removed from the...

 Here is the current gap I'm getting (same one I used to get if I didn't use `wrapInSafeArea={false}`)

@joecampo that is correct, no gap with a closed keyboard. Thank you so much for the help, I'll wait for that PR merge and see if it fixes it. Thank...

Update here: In the latest release (2.0.1), I am able to set `bottomOffset` to `22` to remove the gap. However, this is a workaround and I only tested on two...

@amerikan Just thinking out loud, I might be missing something: - previously, I had `wrapInSafeArea={false}` and handled everything with my own safearea - This means, after wrapInSafeArea was removed, my...

@hirbod That would be perfect and cover the missing use cases yes!