Will we ever be safe from KeyboardAvoidingView?

[@Akshatgiri]

So it's not just me that sucks at dealing with keyboarding avoiding view. I feel so much better now.

[@bawad]

KeyboardAvoidingView gives me nightmares

[@HBMoulvad]

I am working on it right now... and it sucks so hard. Even worse when you have to combine it with a Flatlist or ScrollView.

[@fernandorojo6311]

Until you’ve tried to use KeyboardAvoidingView inside of a react-native-screens/native-stack modal, you haven’t truly seen the darkness.

[@johnhaupenthal]

The support group I really need

[@wcandillon]

So good to see you here John ☺️

[@ArberKryeziu]

Im really enjoying your conversations. Keep it going guys, good work!

[@rafaelcuello3242]

Hello from Dominican Republic 🇩🇴

[@nanakwameacheampong4779]

Oh my God I'm not the only one who hates working on KeyboardAvoidingView on android, this is a very interesting conversation, you guys should really do a live stream, hopefully I'll be able to join

[@BillPairaktaridis]

It's just so ridiculously inconsistent! When you take into account devices that have soft buttons, that don't, that have full screens etc, it's just not gonna work right on 100% of devices. Especially when you have UI situations where you might have a normal TextInput in the middle of the screen but then another that's maybe positioned at the bottom, if you're building a chat functionality in your app, for example.

[@shortkeys73]

William is definitely right that Expo changes windowSoftInputMode between the Expo development client and the built APK. So aggravating

[@ravi.rupareliya]

Hahaha, thank god I am not alone in this one.

[@NicolasSilvaVasault]

i'm literally having issues with this right now LOL, i used to work with keyboard aware scroll view component, it used to work flawless, but then i decided to use the native component, and it has been A NIGHTMARE

[@yalcinozer4434]

It's always a pain using inputs in scrollview and keyboard visible. I developed a number of apps but I still have problems configuring it. If content is not longer than screen height, just give it a minHeigh=deviceHeight, so problem solved. But if it is, its nightmare.

[@jjysoserious]

The struggle is real haha, most relatable video.

[@MatheusGambati]

I feel that I will never master KeyboardAvoidingView. It's hard to identify which view to wrap and it goes on. Only the dead can know peace from this evil.

[@sanathrao2009]

I can totally relate to the problem you just stated. It's a real pain while coding a custom form component

[@anonymousmangalorean]

Add scrollview for user to scroll up

[@SolidousMdz]

I completely agree that it should be named Ios to prove it only works there

[@jonasgroendahl]

every project ever the keyboard avoiding view will ruin everything, my best tip is to wrap keyboard avoiding view in your own component and do platform specific configuration and offsets in order to get it working everywhere

[@mdsarfrazkhan3460]

Hello William Candillon can you discuss about expo-background-fetch why it doesn't work in ios but working fine in android

[@benazirahmed7936]

So why don't we disable it on Android if it already avoids obstructing the view?

[@0906WEST]

The feel of misery. That is EXACTLY the feeling you get. Platform specific paddings and other crap 💩

[@AdityaPahilwani8989]

I use scrollView instead of KeyboardAvoidingView *small hack*

[@neeshsamsi]

What is keyboard avoiding view ?? I'm not into this stuff properly

[@Akshatgiri]

@@neeshsamsi Here's the reference - reactnative.dev/docs/keyboardavoidingview

[@RinKenRyou]

Oh all you guys are in misery too? Goddd hugs for everyone here, ahahahaha. Thanks, I feel much better now.

[@pranavkumar1818]

Bonjour..cant agree more.

[@techabl]

Great guys thanks

[@PeRKoniX87]

No one build a AvoidingKeyboardAvoidingView yet that actually works?

[@mirajshah2302]

Wait what? On android it works without using . The keyboard thing is handled automatically on Android

[@AlexanderPataridze]

AdjustPan isn't the same as iOS. AdjustPan moves whole app window to the top.

[@태평-m1w]

this is totally my story. I once was working in bare project of expo and for some reason had to move on to the managed one and then I became to do this 'KeyboardAvoidingView' and It was not what I had been expecting so I had to move on to the bare project again to modify android xml ahhhhh It was terrible

[@aaqidmasoodi]

it sucks.

[@adarshjaiswal7334]

That show how immature react native really is.