Topi Salonen

We didn't want to update Flow in our project, so I just added a patch using patch-package: ``` diff --git a/node_modules/react-native/flow/global.js b/node_modules/react-native/flow/global.js index b2e76fe..ea6cec7 100644 --- a/node_modules/react-native/flow/global.js +++ b/node_modules/react-native/flow/global.js @@...

Any update for this? We're using `react-native-hms-location` for which I just created a simple patch using `patch-package` that changes the `'maven'` plugin to `'maven-publish'`, which seems to be enough to...

We're upgrading RN to 0.67 and created a `patch-package` patch to fix this issue until we replace this dependency with a maintained one. The patch creates a local `ScrollResponder.js` file...

Any update on this? We have a working patch in our project for this dependency, but it's kind of alarming that there has not been a release with RN 0.75...

We noticed the same issue happening in our e2e pipeline starting yesterday with `macOS-15` as well. It happens with both iOS 18.0 and 18.1 Simulators.

The Simulators worked fine the day before this issue was posted. What changed? Did something update?

Related to this issue Xcode 16 was re-added to the macOS-14 images https://github.com/actions/runner-images/issues/10703#issuecomment-2503985328, so we reverted our pipeline to use that for now.

It feels illegal to use `patch-package` to patch `patch-package` but it does work, thanks. :D I modified the patch a bit for `8.0.0`: ```diff diff --git a/node_modules/patch-package/dist/makePatch.js b/node_modules/patch-package/dist/makePatch.js index d8d0925..9b25269...

Seems like there's also a PR open that includes the changes to support Yarn v2+ properly https://github.com/ds300/patch-package/pull/507