Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RCTFatalException '-[__NSArrayM enumerateKeysAndObjectsUsingBlock:]: unrecognized selector sent to instance 0x170c5b2d0' was thrown while invoking updateView on target UIManager #17265

Closed
peacechen opened this issue Dec 18, 2017 · 1 comment
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@peacechen
Copy link

May be related to
#15755
#14583
#8517

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Yes

Environment

OS:  macOS Sierra 10.12.6
Node:  7.0.0
npm:  3.10.8
Watchman:  4.7.0
Xcode:  Xcode 8.3.3 Build version 8E3004b

Packages: (wanted => installed)
react-native: 0.45.1 => 0.45.1
react: 16.0.0-alpha.12 => 16.0.0-alpha.12

Target Platform: iOS (10.3)

Steps to Reproduce

Our app uses Newrelic for React Native crash analysis. This crash is from an installation "out in the wild". No other known information about this is available.

Expected Behavior

No crash

Actual Behavior

Crashes with the stacktrace:

RCTFatalException: Exception '-[__NSArrayM enumerateKeysAndObjectsUsingBlock:]: unrecognized selector sent to instance 0x170c5b2d0' was thrown while invoking updateView on target UIManager with params ( 12705, RCTText, ( "<__NSCFTimer: 0x170175a80>", "<__NSCFTimer: 0x170175240>", "<__NSCFTimer: 0x170175c00>", "<__NSCFTimer: 0x1701768c0>", "<__NSCFTimer: 0x17017a1c0>", "<__NSCFTimer: 0x1701756c0>", "<__NSCFTimer: 0x170178fc0>", "<__NSCFTimer: 0x170178c00>", "<__NSCFTimer: 0x170178e40>", "<__NSCFTimer: 0x170176740>", "<__NSCFTimer: 0x170170f80>", "<__NSCFTimer: 0x170177640>", "<__NSCFTimer: 0x17016c900>", "<__NSCFTimer: 0x17017a700>" ) )

Reproducible Demo

This crash report came from Newrelic. It's not easily reproducible in the debugger AFAIK.

@stale
Copy link

stale bot commented Feb 16, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 16, 2018
@stale stale bot closed this as completed Feb 24, 2018
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests

1 participant