KeyboardAwareScrollView not auto scrolling to cursor when we type and the cursor is out of view from top of the screen.

[nicolaosm]

Describe the bug
KeyboardAwareScrollView not auto scrolling to cursor when we type and the cursor is out of view from top of the screen.

Code snippet
Added a new clear repo to demonstrate the issue.

Repo for reproducing
Repo: https://github.com/nicolaosm/broken-keyboard/

To Reproduce
Steps to reproduce the behavior:

1. Add caret anywhere on the text.
2. Scroll so that the caret is outside of the view from UP.
3. Type something -> It does not auto scroll to show us where it typed.

Expected behavior
When we type, the view will autoscroll to show us where the cursor is typing. It works fine when the cursor is outside of the view from the bottom, but it does not work when the cursor is outside from the top.

Screenshots
Video: https://cln.sh/mCZ5CN1v

Smartphone (please complete the following information):

Desktop OS: MacOS 26.3
Device: Phone17 Pro Max. (Simulator and Device)
OS: iOS 26.2
RN version: 0.83
RN architecture: New
JS engine: [e.g. JSC, Hermes, v8]
Library version: Commit: #376b27a

Additional context
None.

[kirillzyusko]

I can confirm I can reproduce it - working on a fix 👀

[kirillzyusko]

@nicolaosm could you please check if #1352 fixes the problem for you? 👀

[nicolaosm]

Thanks for the update @kirillzyusko ! I tested the latest version and at first tests it seems working. But there are some situations where it wouldn't work.

Mainly this situation I found that it doesn't work when I add the cursor in the paragraph before the last for some reason, then scroll up so that the cursor is out of the screen from above.

Here's a video: https://cln.sh/vyZXwNLG

I also updated the repo again to help you replicate. Just add the carat in the spot I added the text "Drop Here"

Hope that helps!

[kirillzyusko]

@nicolaosm yes, you are correct! This happens because measureInWindow works incorrectly on Fabric with <Modal presentation="formSheet": facebook/react-native#56062

So in your first case you slightly overscrolled, so the text became rendered behind top bound of Modal, so it scrolls (it works well). Second time it's located "closely" to the end, but since measureInWindow doesn't include top safe area -> it stops to work.

Not sure if you can try to apply a RN patch in your project and check if it works? (you also need to remember that you need to disable precompiled binaries and you need to re-compile code). Or alternatively you can temporarily pass a new property like:

const {top} = useSafeAreaInsets();

// ...

return <KeyboardAwareScrollView topOffset={top} />

And include newly added property in "point" calculation... Though this one seems more like a workaround and I believe issue should be fixed in RN core 🤞

Anyway, let me know what do you think about it! ❤️

[nicolaosm]

@kirillzyusko Thanks for the clarification. So the issue basically is that the cursor is sitting directly behind the top header of the modal and thats why it's not being calculated as being out of the modal view. That makes sense.

In the demo project, the modal I'm using is not the default RN modal, it's the native stack modal from React Navigation. Which I believe is the native iOS modal (it does behave like it as well, I have just disabled to swipe to dismiss). So I don't think the RN patch would solve that.

As for the topOffset prop on the , for some reason it's not being applied. Can you please confirm that prop would work with ?

Thank you!!

[kirillzyusko]

As for the topOffset prop on the , for some reason it's not being applied. Can you please confirm that prop would work with ?

It's not implemented yet 😅

I've tried to use slightly better approach in 5d60c05 But this approach relies on code available in latest main. It kind of works better, but there is still "blind"/"dead" zone when text is already not visible (obscured by header) but text editing doesn't bring it back 😠

Now I think it's caused by the fact that my selection detection aghorithm is not very precise: this is a known issue #1134

My next step would be merging my PR as is and prepare stable 1.21.0 release and I'll ask you again whether I can close this issue or not. If issue is not fixed for you, then I'll add topOffset property to KeyboardAwareScrollView in 1.21.1 and will close this issue!

I'll kep you updated when I prepare a new release 🙌

[nicolaosm]

Thank you @kirillzyusko ! Looking forward for 1.21.0 🙏