Malformed calls from JS: field sizes are different
See original GitHub issue🐛 Bug Report
Here is the bug I get.
Malformed calls from JS: field sizes are different.
[[74,24],[19,1],[[64,2000,1552169087432,false]],415]
RCTFatal -[RCTCxxBridge handleError:] __34-[RCTCxxBridge _initializeBridge:]_block_invoke facebook::react::RCTMessageThread::tryFunc(std::__1::function<void ()> const&) facebook::react::RCTMessageThread::runOnQueue(std::__1::function<void ()>&&):😒_1::operator()() const void std::__1::__invoke_void_return_wrapper<void>::__call<facebook::react::RCTMessageThread::runOnQueue(std::__1::function<void ()>&&):😒_1&>(facebook::react::RCTMessageThread::runOnQueue(std::__1::function<void ()>&&):😒_1&&&) std::__1::__function::__func<facebook::react::RCTMessageThread::runOnQueue(std::__1::function<void ()>&&):😒_1, std::__1::allocator<facebook::react::RCTMessageThread::runOnQueue(std::__1::function<void ()>&&):😒_1>, void ()>::operator()() std::__1::function<void ()>::operator()() const invocation function for block in facebook::react::RCTMessageThread::runAsync(std::__1::function<void ()>) CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK __CFRunLoopDoBlocks __CFRunLoopRun CFRunLoopRunSpecific +[RCTCxxBridge runRunLoop] NSThread__start _pthread_body _pthread_body thread_start
To Reproduce
I was on branch master, everything was working fine. I created a new branch ‘android’ and ran the android simulator, fixing a few things related to android. Then I wanted to make sure things still looked good in iPhone, so I ran to iPhone simulator and that’s when I got the bug. The screen does not crash immediately. It crashes as soon as I login. The android simulator runs completely fine though. I figured I would ‘git checkout master’ branch to pinpoint what exactly caused that error, but the error persisted on the master branch. That doesn’t make much sense to me
Expected Behavior
The iPhone simulator should run fine.
Environment
React Native Environment Info: System: OS: macOS High Sierra 10.13.6 CPU: (8) x64 Intel® Core™ i7-4850HQ CPU @ 2.30GHz Memory: 1.38 GB / 16.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 11.11.0 - ~/.nvm/versions/node/v11.11.0/bin/node npm: 6.7.0 - ~/.nvm/versions/node/v11.11.0/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman SDKs: iOS SDK: Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1 Android SDK: API Levels: 23, 25, 26, 27, 28 Build Tools: 23.0.1, 26.0.1, 28.0.3 System Images: android-23 | Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom, android-23 | Google APIs Intel x86 Atom_64 IDEs: Android Studio: 3.0 AI-171.4443003 Xcode: 10.1/10B61 - /usr/bin/xcodebuild npmPackages: react: ^16.7.0 => 16.7.0 react-native: ^0.58.4 => 0.58.4 npmGlobalPackages: react-native-cli: 2.0.1
Issue Analytics
- State:
- Created 5 years ago
- Reactions:15
- Comments:38 (4 by maintainers)
Top GitHub Comments
It looks like you are using an older version of React Native. Please update to the latest release, v0.59 and verify if the issue still exists.
@Blutude @cristian1703 – upgrading to the latest patch
0.59.1
fixed this issue for me.