Conrad

I have been chasing around trying to figure out the cause of this bug, and, the research of the last two days implicates Detox (although I wish it wasn't so,...

Thank you so much @farcondee ! Confirming that https://github.com/software-mansion/react-native-gesture-handler/issues/722#issuecomment-1014289859 fixed the problem for me.

I'm in the process of upgrading from 0.67.4 to 0.70.1 and I'm blocked by this presently. I watch this thread with interest, and, I'll report back anything that gets the...

In my case I had to rename all instances of `.babelrc` with `babel.config.js` and run the tests with the ` --clear-cache` flag. The additional code in `polyfills/error-guard.js` is not Typescript,...

I have this issue too. node --version = 18.16.0 React Native v0.71.10

Same here, this lane has worked for me in the past too, I'd love to understand a bit more. The error message is cryptic.

Still the same type bug for me with the following versions: ` "@storybook/react-native": "6.0.1-beta.7"` ` "@react-native-async-storage/async-storage": "^1.17.10",`

Yep, still keen, but you know: also quite busy.

I've been having the same error too, this solved it for me: https://stackoverflow.com/questions/67556606/invariant-violation-requirenativecomponent-rnsscreen-was-not-found-in-the-u/67956805#67956805 TL;DR: Normally these pods would be linked automatically but because of monorepo we have to tell the...

Thanks @xiongemi that insight lead the me trying the following which solved this error for me. Adding the following packages in the app's package.json (not the workspace root's package.json) has...