When using multiline={true} in combination with blurOnSubmit={true} the TextInput should blur when enter is pressed. Instead, pressing return inserts a new line.
Tested on both Android and iOS, issue occurs on Android only. iOS works fine.
Using React Native 0.28.0, testing on Android emulator and device, Android version 6.0.1
Sample app: https://rnplay.org/apps/CFQA2A
Bump
Still same issue on 0.33
@kulmajaba @alexprice91 @mmazzarolo Hi folks, I'm checking in to see if this issue is still persisting for you folks.
@ericnakagawa I can't test it right now, I'll give you some feedback the next time I'll use the blurOnSubmit and multiline combo
@ericnakagawa Just checked with React Native 0.40 on Android 7.1.1 device, issue still persists.
@ericnakagawa I can confirm that this issue still exists as of RN 0.42.
The issues still exist in "react-native": "0.43.4" and Android 6
Has anyone had any success with any work arounds? I'm still seeing this issue on 0.46.1
Edit: correction, blurOnSubmit is correctly triggering onSubmitEditing in a multiline with 0.46.4. See https://snack.expo.io/rksUnIh8Z (tested on a Galaxy S6, Android v7.0, Kernel 3.10.61-11656310).
blurOnSubmit is no longer working on the snack provided. Pressing enter only gets me a new line, with no way to submit the TextInput (Expo 21.0.0, React Native 0.48, Nexus 6P, Android 8.0.0)
Just discovered this issue myself, still an issue with React Native 0.50
@richchurcher I can confirm that blurOnSubmit is no longer working on the snack provided. It creates a new line instead of submitting.
Xiaomi Redmi 3S
Android 6.0.1
MIUI 8.5.4.0
blurOnSubmit in combination with multiline works now for me! Using React Native 52.2
These configuration is working as expected for me in react-native v0.55.3
<TextInput
returnKeyType='done'
multiline
autoFocus
blurOnSubmit={true}
autoCorrect={false}
maxLength={1000}
numberOfLines={4}
onChangeText={onTypeComment}
placeholder={I18n.t('SHARE_DETAILS')}
style={styles.textArea}
underlineColorAndroid={'rgba(0,0,0,0)'}
value={comment}
/>
Most helpful comment
@ericnakagawa I can confirm that this issue still exists as of RN 0.42.