React-native-navigation: [iOS] "Malformed calls from JS: field sizes are different."

[shuzootani]

Issue Description

The following error pops up just after launching app.

I assume that I'm doing something wrong with integration of React context API.
So I'd appreciate if someone could point out what I'm doing wrong with using context API and react-native-navigation.

Steps to Reproduce / Code Snippets / Screenshots

I'm wrapping a root screen with React Context API based on this
It doesn't give the error on iPhoneX(12.1) simulator but on some other older versions such as iPhone6(12.1), 6s(12.1).

my index.js looks like below

function registerComponents() {
  Navigation.registerComponent('Detail', () => Detail)
  Navigation.registerComponent('Preview', () => Preview)
  Navigation.registerComponent('Filter', () => Filter)
  Navigation.registerComponent(
    'Search',
    () => props => (
      <SearchContextProvider>
        <Search {...props} />
      </SearchContextProvider>
    ),
    () => Search
  )
}

registerComponents()

Navigation.events().registerAppLaunchedListener(() => {
  Navigation.setRoot({
    root: {
      stack: {
        children: [
          {
            component: {
              name: 'Search',
              options: {
                topBar: {
                  visible: false
                }
              }
            }
          }
        ]
      }
    }
  })
})

---

Environment

• React Native Navigation version: 2.17.0
• React Native version: 0.59.2
• Platform(s) (iOS, Android, or both?): IOS
• Device info (Simulator/Device? OS version? Debug/Release?): Debug on simulators, iPhone6(12.1), 6s(12.1). it only works on iPhoneX simulator somehow.

[AugustoAleGon]

Same problem

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back. Thank you for your contributions.

[reyalpsirc]

Same issue on 0.59.8

[juliettegodyere]

I am also getting this same issue on Android

"react-native": "0.59.8",

[boythan]

Same problem with react-native": "0.59.8",

[DanielBoening]

I have the same problem but only on Android. On iOs it works fine.
react-native 0.59.8
I am using react-native-navigation (v1) 1.1.491

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you believe the issue is still relevant, please test on the latest Detox and report back. Thank you for your contributions.

[stale[bot]]

The issue has been closed for inactivity.

[martinvol]

Have the same issue on react-native 0.59.10

[misterpoloy]

Same for me

[AngelVenchev]

I am having the same issue on Android.

[hellochirag]

Malformed calls from JS: field sizes are different.

[[84,33],[20,0],[[260,2000,1585903674435,false]],3338]

RCTFatal
-[RCTCxxBridge handleError:]
__34-[RCTCxxBridge _initializeBridge:]_block_invoke
facebook::react::RCTMessageThread::tryFunc(std::__1::function facebook::react::RCTMessageThread::runOnQueue(std::__1::function decltype(std::__1::forward void std::__1::__invoke_void_return_wrapper::__call std::__1::__function::__alloc_func, void ()>::operator()()
std::__1::__function::__func, void ()>::operator()()
std::__1::__function::__value_func std::__1::function invocation function for block in facebook::react::RCTMessageThread::runAsync(std::__1::function __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__
__CFRunLoopDoBlocks
__CFRunLoopRun
CFRunLoopRunSpecific
+[RCTCxxBridge runRunLoop]
__NSThread__start__
_pthread_start
thread_start

"react": "16.9.0",
"react-native-navigation": "^6.3.1",
"react-native": "0.61.5",

Don't know why close this issue , if everybuddy facing issue still the day?

[Jarzka]

Same issue here on Android when I call navigator.push. I'm running react-native 0.59.10.

It seems that this only happens once during the lifetime of my app. If I dismiss the error message, I can continue normally. When I restart my app and do navigator.push, it happens again once and then goes away. However, not all navigator.push calls cause this.

I believe this issue should not be closed as many others are also having this problem.

[Jarzka]

I upgraded to RN 0.62 and RN navigation to 0.6.5 and haven't faced this since then.