KeyboardAwareScrollView on android is not as smooth as ios

[caothuyen]

Describe the bug
When the keyboard opens, the content below is pushed up, not as smoothly as on iOS.

Code snippet

function LoginScreen() {
  return (
    <View style={styles.container}>
      <View style={styles.background}>
        <LinearGradient
          colors={["#114395", "#195DCE", "#1F6BF2", "#0A89E2", "#fff"]}
          locations={[0, 0.135, 0.36, 0.45, 0.625]}
          style={[styles.background, styles.backgroundLinear]}
        />
        <LogoLine style={[styles.logoLine, styles.background]} />
        <NetworkLine style={[styles.networkLine, styles.background]} />
      </View>

      <KeyboardAwareScrollView style={styles.scrollView} showsVerticalScrollIndicator={false}>
        <View style={styles.content}>
          <Image source={require("assets/images/icon.png")} style={styles.logo} fadeDuration={0} />
          <Text style={styles.title}>Chào mừng đến với Quốc Duy</Text>
          <RenderForm />
          <TextInput style={{ height: 48, borderWidth: 1, borderColor: "red" }} placeholder="press input" />
          <TextInput style={{ height: 48, borderWidth: 1, borderColor: "red" }} placeholder="press input" />
          <TextInput style={{ height: 48, borderWidth: 1, borderColor: "red" }} placeholder="press input" />
        </View>
      </KeyboardAwareScrollView>
    </View>
  );
}

Expected behavior
On android can be as smooth as ios

Screenshots

Screen.Recording.2024-12-04.at.09.46.42.mov

Screen.Recording.2024-12-04.at.09.47.07.mov

I tested on real device and production environment but still not effective

• Desktop OS: MacOS 15.1.1
• Device: iPhone 14 Pro Max and Android pixel 6 pro
• OS: iOS 17.5 and android 12
• RN version: 0.76.3
• RN architecture: paper/fabric
• JS engine: Hermes
• Library version: 1.14.5

[caothuyen]

This code in RenderForm

function RenderForm() {
  const handleLogin = async (username, password) => {
    await Login(username, password);
  };

  return (
    <View style={styles.formContainer}>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <FieldWrapper label="Mật khẩu">
        <Input iconLeft="fa-key" iconRight={<RenderShowPassword />} secureTextEntry />
      </FieldWrapper>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <FieldWrapper label="Tên đăng nhập">
        <Input iconLeft="fa-user" />
      </FieldWrapper>
      <AnimPress onPress={() => handleLogin("*****", "*****")}>
        <View style={styles.buttonSubmit}>
          <Text style={styles.buttonSubmitText}>Đăng nhập</Text>
        </View>
      </AnimPress>
    </View>
  );
}

const FieldWrapper = memo(({ children, label }) => (
  <View style={styles.fieldWrapper}>
    <Text style={styles.fieldLabel}>{label}</Text>
    {children}
  </View>
));

const RenderShowPassword = memo(() => {
  return (
    <TouchableOpacity onPress={() => {}} activeOpacity={0.8}>
      <FaIcon icon="fa-eye" size={16} color={colors.dark_gray} />
    </TouchableOpacity>
  );
});

[kirillzyusko]

Hi @caothuyen

This is how animation looks on my Pixel 7 Pro (Android 15) - tested in example app:

telegram-cloud-document-2-5368776602526179445.mp4

I don't have any missing frames - would you mind to create a reproducible example (including all styles) so that I can copy/paste it into my example app?

[caothuyen]

Here is the example source code: https://github.com/caothuyen/example.git the page I recorded in the video is located at src/screens/User/Login

[kirillzyusko]

Thanks @caothuyen for a reproduction! Checking it today 👀

[kirillzyusko]

@caothuyen getting this:

> Task :expo-updates:kspDebugKotlin FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':expo-updates:kspDebugKotlin'.
> java.io.StreamCorruptedException: unexpected EOF in middle of data block

When try to build the app. Any ideas why?..

[shuo-hiwintech]

Code to run this example on Android:

react-native-keyboard-controller/example/src/screens/Examples/ReanimatedChatFlatList/index.tsx

Line 46 in 0ce68ed

function ReanimatedChatFlatList() {

The actual result is very choppy and jerky up and down on Android, very flowy on IOS.

"react-native": "0.76.2".
"react-native-keyboard-controller":"^1.14.5",
"react-native-reanimated":"^3.16.2",

[kirillzyusko]

@shuo-hiwintech which Android version do you use? Which RN architecture do you use? Can you attach a video? Is it reproducible in emulator?

telegram-cloud-document-2-5426846321304701690.mp4

This is how it looks on my Pixel 7 Pro (Android 15, REA 3.16.1, paper/old architecture) 👀

[shuo-hiwintech]

@shuo-hiwintech which Android version do you use? Which RN architecture do you use? Can you attach a video? Is it reproducible in emulator?

telegram-cloud-document-2-5426846321304701690.mp4
This is how it looks on my Pixel 7 Pro (Android 15, REA 3.16.1, paper/old architecture) 👀

Thanks for the quick response, I'm using your library in another project with a new non-RN architecture and it's running great.

The status of my new project:

"react-native": "0.76.2", yes I'm using the new RN architecture.

Android real machine information:
REDMI K80
Android version 15

Screenrecorder-2024-12-24-19-21-46-176.mp4

（Shaky video recording, recorded at 90 fps）

[shuo-hiwintech]

@shuo-hiwintech which Android version do you use? Which RN architecture do you use? Can you attach a video? Is it reproducible in emulator?

telegram-cloud-document-2-5426846321304701690.mp4
This is how it looks on my Pixel 7 Pro (Android 15, REA 3.16.1, paper/old architecture) 👀

My code:

import {FlatList, Text, View} from 'react-native';
import {useKeyboardHandler} from 'react-native-keyboard-controller';
import Animated, {
  useAnimatedStyle,
  useSharedValue,
} from 'react-native-reanimated';

import Input from '@/components/Input';

const useGradualAnimation = () => {
  const height = useSharedValue(0);

  useKeyboardHandler(
    {
      onMove: e => {
        'worklet';

        height.value = e.height;
      },
      onEnd: e => {
        'worklet';

        height.value = e.height;
      },
    },
    [],
  );

  return {height};
};

const Home = () => {
  const {height} = useGradualAnimation();

  const fakeView = useAnimatedStyle(
    () => ({
      height: Math.abs(height.value),
    }),
    [],
  );

  return (
    <View style={{flex: 1}}>
      <FlatList
        inverted
        data={Array.from({length: 50})}
        initialNumToRender={15}
        renderItem={({_, index}) => {
          return (
            <View>
              <Text style={{color: 'pink'}}>{index}</Text>
            </View>
          );
        }}
      />

      <View
        style={{
          backgroundColor: '#ec7373',
          padding: 10,
        }}>
        <Input placeholder={' leave your comment here.'} />
      </View>

      <Animated.View style={fakeView} />
    </View>
  );
};

export default Home;

[shuo-hiwintech]

@shuo-hiwintech which Android version do you use? Which RN architecture do you use? Can you attach a video? Is it reproducible in emulator?

telegram-cloud-document-2-5426846321304701690.mp4
This is how it looks on my Pixel 7 Pro (Android 15, REA 3.16.1, paper/old architecture) 👀

Unfortunately, it's not possible to replicate this on an android emulator, I suspect it should be possible to replicate it on a real android machine. : (

[kirillzyusko]

@shuo-hiwintech well, I think I encounter a similar issue, when performance on a new architecture is not as great as on old architecture. The only one thing that I discovered is that only non-UI props (such as height) are problematic. If you animate translateY then everything works well.

Maybe it's because of not very optimized ShadowTree traversal on reanimated side (but honestly I don't know a root cause, so it's only my guesses). Let me run fabric example on my devices and get back to you!