Kudo Chien

@maxenceg we would like to publish patch release with the other fix together, and it should be available within this week.

hi there! i would have some thought for this issue on expo go and i would like to check for more information. @jnoleau is your app built by eas build...

oh no, if it is eas build app, i don't have thought in the mean time. supposedly, the react-native would likely to have similar issue. maybe this one: https://github.com/facebook/react-native/issues/33896

if someone can repro the crash in house and could help to verify whether the updated jsc fixing the crash, that would be appreciated. upgrade steps (for EAS build only)...

@codal-mpawar does it work for you if you remove expo-updates by `yarn remove expo-updates`?

@codal-mpawar the problem without expo-updates should be different case. could you share the crash log without expo-updates?

> I tried this in a "distribution": "internal" build, but app it's not even opening. It crashs right after launching and before splash screen. @tinchogon34 could you share the crash...

@codal-mpawar is your crash happening only on samsung devices? if you could provide a minimal reproducible example, that would help us to further investigate.

reanimated didn't officially support v8 now. [in the meantime i just forked and build v8 aar by myself.](https://github.com/Kudo/react-native-v8/issues/64#issuecomment-939992153) and here is how i check which aar to use: https://github.com/Kudo/react-native-reanimated/commit/4b069950c4b75b836350b1803485819939ce632b#diff-d260c332176b5c72008900aef1116a89a873451c7388a808c8d2d58be0865d38R64-R65

hi there! i am happy to help, but it's hard for me to investigate a problem i cannot reproduce. could you help to provide a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) for me...