Renaud Chaput

I can confirm this on my app, it happens with both iOS and Android after upgrading from RN 0.69.4 to RN 0.70.0

As mentioned in https://github.com/facebook/react-native/issues/34665, using `` fixes the issue. This is a workaround until the real `Animated` bug is fixed, I tested it both on Android and iOS.

I am seeing a similar issue: ``` ❌ /Users/renchap/dev/project/packages/mobile/ios/Pods/Headers/Private/React-Codegen/react/renderer/components/rncore/EventEmitters.h:12:10: 'react/renderer/components/view/ViewEventEmitter.h' file not found #include ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ```

I removed my `ios/build/` and `ios/Pods/`, rebuilt everything, and it now compiles with RN 0.68.0. @AlexanderEggers have you tried this?

Thanks for your report. This is weird as there is no `import … from "react-dom/client"` but a dynamic import (`await import('react-dom/client')`) which should be resolved at runtime and a failure...

I tested this PR with my app (browser only) and it still works. Tests are passing.

This is still valid, at least those 2 internal components are using unsafe callbacks: - `AnimatedComponent` - `ScrollViewStickyHeader` It looks like `ScrollViewStickyHeader` was converted to a function component at some...

I am used to working with a lot of photos (I created notos.co) and I am familiar with these issues. A few ideas from my experience: - browser-side image resizing...

Having switched from `imagemagick` to `vips` in a major project, I can confirm all the advantages @matthewford described above. The security aspect is major and the speed/memory boosts are impresive....

This migration is probably a good idea, but will be a huge undertaking in both: - the needed code changes - the migration on every instances I am not (yet)...