Unable to focus KeyboardExtendedInput on Android on Expo 53 / React Native 0.79.

[pehagg]

After upgrading our app we no longer receive focus when tapping the KeyboardExtendedInput. I get the same behaviour when I create an app from scratch, so it shouldn't be an issue in our codebase. Regular TextInput works just fine, but react-native-external-keyboard's TextInput sports the same problem.

Using 0.6.1 with Expo 53.0.20 and React Native 0.79.5.

Example code:

    <View style={styles.container}>
      <Text>First name</Text>
      <TextInput style={{ borderWidth: 1, borderColor: 'hotpink' }} value={firstName} onChangeText={setFirstName} multiline />
      <StatusBar style="auto" />
    </View>

Anyone else run into this?

[ArturKalach]

Hello @pehagg,
It seems that Meta has fixed the issue with TextInput in React Native 0.80.x. About a month ago, they also released a fix for version 0.79.5. I’ve already made some updates for 0.80.x, but it looks like these updates should also be applied to 0.79.5.

Additionally, I think you could consider migrating from KeyboardExtendedInput to the default TextInput, as it appears to work fine with the keyboard so far.

I created an issue based on the discussion and am going to fix it as part of that.

[pehagg]

I noticed there is a slight difference in behavior when using the stock TextInput. With it the control is in edit mode immediately, while with KeyboardExtendedInput you need to press either space or return to enter edit mode. Our designer would prefer this press--to-edit behavior, but I guess it's not possible anymore?

[pehagg]

Additionally, as were Expo users we're stuck with RN 0.79 until Expo 54, which will be released later. Would be great to get stuff working with 0.79.

Thanks for addressing the issue, and even greater thank you for providing such great a11y libraries!

[ArturKalach]

Hello @pehagg,
I created a fix for this as part of the 0.6.2 release.

Regarding the press-to-edit behavior, I believe it’s possible. However, the last time I attempted to fix the issue for React Native 0.80.x, I couldn’t find a simple solution. I think it makes sense to create another component specifically for React Native 0.79.x and higher, but at the moment, I have other priorities.

I will try to check it, but not sure when I will have some time for this.

My main focus right now is to refactor the package. There are many areas that need updates and improvements, as well as several pending ToDos. Additionaly, I am going to add some functionality for react-native-a11y-order.

[pehagg]

Thank you for your swift action and I understand that this is not high priority.

I think we can live with the new behavior for a while, it's mainly meant for improving UX while using Talkback, if I understood our designer correctly. Higher priority is to get a working focus when tapped.