upgrade-support
upgrade-support copied to clipboard
Help/Advice: RCTFatal error when upgrading to 0.63.4
Environment
Things I’ve done to figure out my issue
- [X] I used upgrade-helper to do my upgrade.
- [X] Check of the library I use to see if they are compatible with 0.63.4 RN version
Upgrading version
0.63.4
Description
Hi, I'm attempting to upgrade my react native project to version 0.63.4 from version 0.61.5.
I managed to get the build working by following the dedicated upgrade helper for my migration (https://react-native-community.github.io/upgrade-helper/?from=0.61.5&to=0.63.4)
I however still have one major issue, when running the app on the Simulator, once the bundle work finished I'm instantly getting an RCTFatal
error, which doesn't really give me any indication as to where the problem comes from.
Here is a copy of the error shown on the iOS simulator.
RCTFatal
__28-[RCTCxxBridge handleError:]_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_callback_4CF
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
-[UIApplication _run]
UIApplicationMain
main
start
0x0


-
Does anyone has ever seen such an error? Am I missing something?
-
Is there anything I can do to get more debug/error info?
(Note: I'm familiar with iOS development but I'm more from low-level language background and since the beginning of my career JS and Android development so I must I am a bit of a newbie regarding xCode, I know basic but not necessarily all the caveats when going about debugging).
Thanks for your help,
Antoine Mace
Reproducible demo
Not applicable
I am experiencing exactly the same issue
Same here, any fix on this? please help.
experiencing the same issue