search

robwalkerco / redux-persist-filesystem-storage

Redux persist adaptor for React Native filesystem storage
MIT License
196 stars 71 forks source link

Error in callNativeModules() malformed calls from JS: field sizes are different #13

Closed maraujop closed 6 years ago

maraujop commented 6 years ago

captura de pantalla 2018-04-25 a las 16 58 19

Almost went bananas today, trying to find out what was causing this error. Apparently this field sizes are different is the "human friendly" way of RN of telling you that parameters passed to the native code from javascript don't match.

After debugging pretty much the whole storage, I found that this module contains a copy of react-native-fetch-blob under node_modules of the library, which was colliding with the version I'm using in my own app. After deleting this one, everything started working like a charm.

I'm opening this issue as a future reference for anyone hitting the same stone and just in case you have a tip on how to better handle this scenario.

Thank you very much, cheers Miguel

mamaz commented 6 years ago

I had also a case like this when Native implementation is different than JS. For example, on Native you use Promise, but on JS you use callbacks.

Not related, but hopefully will help anyone facing this issue.

robwalkerco commented 6 years ago

Closing due to lack of activity on this issue. Please reopen if further discussion is required.

mopilo commented 6 years ago

what's the solution this this error?? @maraujop did you find a solution??

robwalkerco commented 6 years ago

It’s not clear that this error is caused by this package.

Are you able to replicate in a minimal example that’s shows that this package is at fault?

mopilo commented 6 years ago

okay, i feel it has to do with redux

robwalkerco commented 6 years ago

@mopilo The solution for the error is actually in the initial issue (https://github.com/robwalkerco/redux-persist-filesystem-storage/issues/13#issue-317694059)

I think that deleting your node_modules folder and running npm install or yarn will likely fix it :)

AppleMango23 commented 5 years ago

for this one i solve it by filter the input variable that i wanted to use in my code and this error disappeared. Try check the variable that u are using.