[Xcode 11] [iOS 13] EXC_BAD_ACCESS in fishhook.c

Bug

When running my app on an iPhone XR (iOS 13), the app immediately crashes with EXC_BAD_ACCESS.

I can only reproduce this when running on a physical iPhone. iPad and simulator both work fine.

Environment info

React native info output:

 info
  React Native Environment Info:
    System:
      OS: macOS 10.15
      CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
      Memory: 1.78 GB / 16.00 GB
      Shell: 5.7.1 - /bin/zsh
    Binaries:
      Node: 8.16.0 - ~/.nvm/versions/node/v8.16.0/bin/node
      Yarn: 1.16.0 - /usr/local/bin/yarn
      npm: 6.4.1 - ~/.nvm/versions/node/v8.16.0/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 13.0, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
    IDEs:
      Android Studio: 3.4 AI-183.6156.11.34.5522156
      Xcode: 11.0/11M336w - /usr/bin/xcodebuild
    npmPackages:
      react: 16.8.6 => 16.8.6
      react-native: ^0.59.9 => 0.59.9

Library version: 0.59.9

Steps To Reproduce

Make a new React Native project with react-native init and run on device.

Describe what you expected to happen:

1. App to not crash immediately

Reproducible sample code

Here That’s a link to a repo I just made for a test project.

EDIT: Fixed the link to the repo

[xeric]

For you guys who are still working on 0.59.10 and hard to apply 46bdb41 patch in to your local. Go to ‘node_modules/react-native/Libraries/fishhook/fishhook.c’ and delete whole method ‘perform_rebinding_with_section’ content, keep the method definition. Save -> Done.

[GleidsonDaniel]

The curious thing is that this error only happens on iphones 11, on inferior devices like X, the error does not happen …