[iOS] Thread 1: signal SIGABRT when running on iPhone 8 iOS 13.3.1

[duyanhv]

Description:

The app works fine on simulator (iPhone 8 iOS 13.3.1)   but when I used Xcode to built and ran on a real device (iPhone 8 iOS 13.3.1),   the app crashed on splash screen with Thread 1: signal SIGABRT

With the error in the debug console:

React Native version:

System:
OS: macOS 10.15.3
CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 451.29 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh

Binaries:
Node: 12.14.1 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.13.4 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 23, 24, 27, 28, 29
Build Tools: 28.0.3, 29.0.1
System Images: android-24 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.6010548
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
npmGlobalPackages:
react-native-vector-icons: 6.6.0

Steps To Reproduce

Provide a detailed list of steps that reproduce the issue.
Issues without reproduction steps or code are likely to stall.

1. react-native run-ios --device 'name of the device'

Expected Results

The app running without thread 1 SIGABRT

Snack, code example, screenshot, or link to a repository:

[safaiyeh]

Hi @duyanhv thank you for the issue. We need a couple things from you to investigate more.

1. Run react-native info and paste the output in your issue.
2. Verify this happens on the latest version of RN
3. Provide a reproducible Snack or repository that demonstrates this issue.

[stale]

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

[stale]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.