Right now my chat screen looks like this:
<View style={{flex: 1}}>
<Header {props...} />
<GiftedChat {props...}/>
</View>
When I press the "Type a message" bar at the bottom and the keyboard appears, my Header disappears, how do I make it stick?
I tried giving the header position: absolute, but it didn't help and also made the header un-clickable!
Thanks!
Hello, did you find a solution ?
@zarnifoulette No, right now I have just accepted it, haven't had time to look into it anymore.
Would be great if someone had a solution! 馃
It will be great to be able to provide headerCompontent which will be displayed as a first element in the chat and be part of the message scroll
I solved this problem replacing android:windowSoftInputMode="adjustPan" to android:windowSoftInputMode="adjustResize" in AndroidManifest.xml. Don't forget to rebuild your application after any changes in AndroidManifest.xml, cause your current build won't see the difference.
But what if other screens need adjust pan? I dont think its feasible to just change the manifest file
Did someone find a solution to this issue?
I'm developping an app which is using react-native-gifted-chat and i have the same issue
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Any idea on how to solve this? This only happens on Android for me. I'm using NativeBase's header. Whenever the keyboard is opened, my entire header disappears because is being pushed to top lol.
Have the same issue, would be great to have a solution!
@maxim-kushnarov-dev-optima i fixed it by using adjustResize in AndroidManifest.xml, i had a wrong android:windowSoftInputMode
@msqar But it will accept adjustResize for all screens, or could we make it only for screen where we have a chat ?
@maxim-kushnarov-dev-optima unfortunately, nope. Although the best one to use is adjustResize otherwise it will push the content up, and that's pretty undesired.
@msqar Thanks, it was very helpful!
I am also facing the same issue, would be great to have a solution!