App instantly crashes in v0.53.3 on iOS due to a low-level RedBox error

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

Environment: OS: macOS High Sierra 10.13.3 Node: 9.5.0 Yarn: 1.3.2 npm: 5.6.0 Watchman: 4.9.0 Xcode: Xcode 9.2 Build version 9C40b Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed) react: 16.2.0 => 16.2.0 react-native: 0.53.3 => 0.53.3

Steps to Reproduce

I’m not entirely sure, as there’s a chance it might have to do with XCode, Objective-C, or something else low-level. After upgrading to v0.53.3, my app instantly crashes the minute it loads. I removed my ios directory, ejected the project and re-linked all my dependencies and received the same error. Running react-native log-ios outputs an Objective-C runtime error that I’m not quite sure how to interpret (see below).

Expected Behavior

I imagined there would be some RedBox errors after upgrading, but the app now crashes before it can even display those errors due to a runtime issue.

Actual Behavior

The app crashes. Running react-native log-ios I see the following output:

Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UITableView heightAnchor]: unrecognized selector sent to instance 0x7fde20865400'
	*** First throw call stack:
	(
		0   CoreFoundation                      0x000000010b8ccf35 __exceptionPreprocess + 165
		1   libobjc.A.dylib                     0x000000010aa28bb7 objc_exception_throw + 45
		2   CoreFoundation                      0x000000010b8d404d -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
		3   CoreFoundation                      0x000000010b82c27c ___forwarding___ + 988
		4   CoreFoundation                      0x000000010b82be18 _CF_forwarding_prep_0 + 120
		5   MyApp                               0x0000000109e6bd2c -[RCTRedBoxExtraDataViewController init] + 2524
		6   MyApp                               0x0000000109ed11f6 __55-[RCTRedBox showErrorMessage:withParsedStack:isUpdate:]_block_invoke + 70
		7   libdispatch.dylib                   0x000000010e6b0af6 _dispatch_call_block_and_release + 12
		8   libdispatch.dylib                   0x000000010e6caaf4 _dispatch_client_callout + 8
		9   libdispatch.dylib                   0x000000010e6b6265 _dispatch_main_queue_callback_4CF + 490
		10  CoreFoundation                      0x000000010b834fe9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
		11  CoreFoundation                      0x000000010b7f7eeb __CFRunLoopRun + 2043
		12  CoreFoundation                      0x000000010b7f7486 CFRunLoopRunSpecific + 470
		13  GraphicsServices                    0x000000010fb549f0 GSEventRunModal + 161
		14  UIKit                               0x000000010d2c5420 UIApplicationMain + 1282
		15  MyApp                               0x0000000109d93caf main + 111
		16  libdyld.dylib                       0x000000010e6fa145 start + 1
		17  ???                                 0x0000000000000001 0x0 + 1
	)

Checking RCTRedBoxExtraDataViewController.m, I saw the “heightAnchor” calls the error is referencing. That said, I’m not exactly sure how to approach this issue or why it might be happening in the first place. If I had any clue what kind of RedBox error it might be trying to throw or what is causing that error I’d have a better shot of replicating it, but right now I’m rather in the dark.

Any idea what could trip up the RedBox system like that? Is there another way to view what error it’s trying to throw so I can at least better understand why the error is causing the app to crash? Any help is appreciated. Thanks.

[poison]

I’m experiencing the same issue

-[UITableView heightAnchor]: unrecognized selector sent to instance 0x15099600 *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[UITableView heightAnchor]: unrecognized selector sent to instance 0x15099600’

Ran from Xcode (not the command-line) on iOS 8.1.2, iPhone 5

[stale[bot]]

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.