You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the RCTBridge.enqueueJSCall we have asserts that checks that moduleID and methodID are never null, however in a release build they will be skipped, so we will end up with a crash because arguments array cannot be created with null values.
The text was updated successfully, but these errors were encountered:
Here the pull request that fixes this issue. While I'm a bit concerned how we can create a unit-test for that.
And actually the bigger question is - should it be fixed? If yes, then we have to go through all RCTAssert and check that in never fails afterwards, but at the same time the whole point of RCTAssert is to tell that we faced unexpected. What it is your thoughts about it?
Hi,
In the RCTBridge.enqueueJSCall we have asserts that checks that moduleID and methodID are never null, however in a release build they will be skipped, so we will end up with a crash because arguments array cannot be created with null values.
The text was updated successfully, but these errors were encountered: