[iOS] Reduced motion + Prefer Cross-Fade Transition: onKeyboardMoveEnd has incorrect values when keyboard opens (height: 0, progress: 0)

[matthieugicquel]

Describe the bug

On iOS, with reduced motion and prefer cross-fade transition enabled, onKeyboardMoveEnd is systematically called with incorrect values after the keyboard opens:

{
    "height": 0, // expecting ~318
    "progress": 0, // expecting 1
    "duration": 383,
    "target": 946,
    "eventName": "onKeyboardMoveEnd"
}

Code snippet

  useKeyboardHandler({
    onEnd: (event) => {
      "worklet";

      console.log("onEnd", event)
    },
  });

Repo for reproducing

I'm having issues building the FabricExample app right now, but I'm still opening the issue in the meantime as I'm relatively confident it will be reproducible in it :)

To Reproduce

1. Toggle the settings in accessibility → animation
2. Open the keyboard
3. Look at the logs

Expected behavior
Height and progress values coherent with cases where those settings are not enabled.

Smartphone

• Device: iPhone 16 Pro / iPhone 16 Pro Max
• OS: iOS 26.0 / iOS 26.1
• RN version: 0.81.5
• RN architecture: fabric
• JS engine: hermes
• Library version: tested on main in FabricExample

[kirillzyusko]

@matthieugicquel is it iOS 26 specific?

[matthieugicquel]

@matthieugicquel is it iOS 26 specific?

I only got reports and reproduced on iOS 26, I don't know if the issue was présent before...

[kirillzyusko]

@matthieugicquel before it was working well 🙃 I explicitly fixed it, but now on iOS 26 Apple fires keyboardDidShow too early (not after 500ms when keyboard finished its movement). If Apple would respect to animation timing then it would work properly, but they literally send event "animation completed" but the animation is in the progress 🤷‍♂️

[kirillzyusko]

We also have similar open issue: #1141

[Daniel3711997]

@kirillzyusko Any idea when a fix for this will be released? Thank you!

[anoopmm]

@kirillzyusko Same issue for me as well. KeyboardAvoidingView does not work correctly when Prefer Cross-Fade Transition is enabled. Keyboard covers the input field in our chat application, and the user is unable to access the input box. Is there any fix for it?

[kirillzyusko]

@matthieugicquel @Daniel3711997 @anoopmm will #1161 fix the issue for you?

[anoopmm]

@kirillzyusko It's working fine now with these changes applied

[Daniel3711997]

Can this be released? Thank you :)