PierreCapo

Oh perfect, thanks for trying and good to know. Let's do this yeah, I'll let this issue opened until expo SDK 50 is released 👍

@baronha I still have the issue on my side with 2.0 even if I force the language with the `language` option.

@tjclawson-stripe kotlinVersion used is "2.0.21". @porter-stripe excuse-me I don't understand your question: - Given I am using react-native, I haven't registered anywhere in my project any jetpack compose version (I...

As a workaround, downgrading to `rive-react-native: 7.0.5` work on my side 👍

Hello @HaleyRevcat I haven't checked again, but I am setting up a new project on Android in a few weeks, so I will let you know if I can see...

@lancesnider @HayesGordon sorry in advance for pinging you, but do you have any visibility on when this is going to be fixed? This issue has been opened for 3 months...

Same, most likely an issue related with the static linking for frameworks enforced by React-Native Firebase

Fixed in the last commit e9fa1010a287cc87f4ffeb5a2a4166661f1fa5cb 🎉 Working on my side

Same issue here. For Azerty keyboards the fix provided by @Chabulga works with the same values that he has provided on his screenshot, although at first it seems it doesn't...

As a workaround, you can use the old swipeable component that doesn't have this problem. ``` import Swipeable from 'react-native-gesture-handler/ReanimatedSwipeable'; // replace by import {Swipeable} from 'react-native-gesture-handler'; ```