iOS 13 and above EXC_BAD_ACCESS KERN_INVALID_ADDRESS acebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_delete<facebook::react::RAMBundleRegistry> >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >)

This started happening after iOS 13 was release. I started seeing a lot of crashes in productions with this in my fabric logs.

Crashed: com.apple.root.user-interactive-qos 0 member_mobile_update_prod 0x100172910 facebook::react::Instance::loadApplication(std::__1::unique_ptr<facebook::react::RAMBundleRegistry, std::__1::default_delete<facebook::react::RAMBundleRegistry> >, std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >) + 414720 1 member_mobile_update_prod 0x100172bec facebook::react::Instance::loadScriptFromString(std::__1::unique_ptr<facebook::react::JSBigString const, std::__1::default_delete<facebook::react::JSBigString const> >, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, bool) + 415452 2 member_mobile_update_prod 0x1000fe1ec __51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke + 4305887724 3 member_mobile_update_prod 0x100120148 facebook::react::tryAndReturnError(std::__1::function<void ()> const&) + 76856 4 member_mobile_update_prod 0x1000f8474 -[RCTCxxBridge _tryAndHandleError:] + 4305863796 5 member_mobile_update_prod 0x1000fdee8 -[RCTCxxBridge executeApplicationScript:url:async:] + 4305886952 6 member_mobile_update_prod 0x1000fdcdc -[RCTCxxBridge enqueueApplicationScript:url:onComplete:] + 4305886428 7 member_mobile_update_prod 0x1000fba20 -[RCTCxxBridge executeSourceCode:sync:] + 4305877536 8 member_mobile_update_prod 0x1000f927c __21-[RCTCxxBridge start]_block_invoke_2 + 4305867388 9 libdispatch.dylib 0x18f28fbb0 _dispatch_call_block_and_release + 32 10 (Missing) 0x3d3a84818f291000 (Missing) 11 (Missing) 0x0 (Missing) 12 (Missing) 0x0 (Missing) 13 (Missing) 0x177bf7018f2f6a00 (Missing) 14 (Missing) 0x0 (Missing)

React Native version:

React Native Environment Info:
System:
  OS: macOS 10.14.6
  CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
  Memory: 33.30 MB / 16.00 GB
  Shell: 3.2.57 - /bin/bash
Binaries:
  Node: 10.8.0 - ~/.nvm/versions/node/v10.8.0/bin/node
  Yarn: 1.13.0 - ~/.nvm/versions/node/v10.8.0/bin/yarn
  npm: 6.10.2 - ~/.nvm/versions/node/v10.8.0/bin/npm
  Watchman: 4.7.0 - /usr/local/bin/watchman
SDKs:
  iOS SDK:
    Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
IDEs:
  Android Studio: 3.3 AI-182.5107.16.33.5264788
  Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
npmPackages:
  react: 16.8.3 => 16.8.3 
  react-native: 0.59.10 => 0.59.10 
npmGlobalPackages:
  react-native-cli: 2.0.1

Steps To Reproduce

1. I am not able to reproduce this but similar issue was found in 0.59.5 in iOS so we upgraded to 0.59.10 thinking it will fix the issue but it is still happening in production.

I cannot updated to latest RN because of Android X changes.

[oleksandr-dziuban]

I have same issue on react-native 0.61.2 on iOS 13 https://github.com/facebook/react-native/issues/26746

[gnprice]

At this point it’s no longer helpful to add more reports of seeing the issue on RN v0.59. I think it’s no longer helpful to report seeing it even on RN v0.61, now that v0.62 is out.

What would be very helpful is a report for v0.62, the latest version. (Or better yet, the v0.63 release candidate!)

If you’re looking at this thread because you’re seeing this issue, and your app is using v0.62 (or later): please add a comment with details like @luatnd’s https://github.com/facebook/react-native/issues/26985#issuecomment-596986763 😄

Until then the developers of React Native will effectively assume the issue was fixed in v0.62, and ignore it to focus on the many other things on their to-do list. That’s what, as I read it, the label “Needs: Verify on Latest Version” means.

And if you’re reading this in the future, and someone has already reported it on v0.62 and a newer release is out (but this thread doesn’t show a fix yet): same thing applies, just increment all the version numbers in this comment.