-
Notifications
You must be signed in to change notification settings - Fork 157
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
Invariant Violation [923, "RCTImageView" ... ] is not usable as a native method argument #105
Comments
I have same problem! >.< |
are you using the same version of react-native ? 0.58.1 ? @Lang-le |
@abdul-elah-js I use React Native 0.58.3. |
could it be because of the whole .58 version ? i read the changelog but i don't remember finding anything relevant about the |
@abdul-elah-js You might see some logs in the console, or I would try directly creating an image element with that URL and see if there are any issues with it. |
@brh55 |
@abdul-elah-js |
@brh55 I tried giving the image a height, width and resizeMode but still i got the same error without any logs, the weirdest thing though is this error is only triggered after running perfectly for the first time !, |
@Lang-le I did the same 👍🏽 |
Help me I also facing the same error.
|
I have same problem! The images success to display at the first time, but It show errors the next time
|
Is this android or iOS? @mingxin-yang |
android @brh55 |
this is solved? i got same error |
Update, error stems from the fact that Clearly, this is an important basis for calculating appropriate image resizing, hence the |
Facing the same issue. It has to be something with cache. Coz I am not getting the error on first run or after I clear the cache. Could this be because local images (cached, that become local once cached) need height and width to be passed as props or there's no such thing? |
I added width and height to my brick object and it seems to have fixed the issue for me. |
@hack-and-backslash Issue comes from the fact Adding height and brick will work in theory, but we really don't want users to be doing that as it will result in potential funky behavior :3. |
still same error "react-native-masonry": "^0.5.0-alpha.4", How can I add width and height to the brick data? |
Just like you add other stuff like uri, onPress etc.
But again, as @brh55 says, it might result in potential funky behavior. I haven't found anything funny yet though. |
The odd behavior is the first "brick" will render with incorrect resize dimension, but it should promptly fix itself with the correct dimensions on the second re-render. Ironically, this might be a hotfix solution by giving the parent default dimensions. |
I tried severally, but failed. -If I use the normal image views, the red screen is shown as followed
-When I use the FastImages, the result....
How can I handle masonry? |
same error
|
give the node_modules\react-native-masonry\components\Masonry.js 's dimentsions a default value and edit node_modules\react-native-masonry\components\Column.js line:64 this works for me |
This works for me |
This does work as long as the parent element has no padding around your Masonry. I'll take this as PR fix if anyone wants to submit. I've been struggling to come up with a clean fix to support the masonry being placed anywhere since the changes to onLoad. I appreciate all the eyes and support on this! 💃 |
Same here (RN by expo sdk33 : 0.59.8 , react 16.8.3), if you can send width/height in bricks it passes the first time... |
In my case, I had an error : "RCTView", in this line: <View style={{alignItems: 'center', position:'relative', left: (window.width/2), top:50, flexDirection: 'column'}}> in my file. |
Please focuse correct id. It will work perfectly. |
Is there any way to fix this without modifying the package? |
Expected Behavior
To Render The Masonry Images
Current Behavior
Breaks Down
Context (Environment)
1- react v16.6.3
2- react-native v0.58.1
react-native-masonry v^0.5.0-alpha.3
All I want to do is to render a simple Masonry but i keep getting this error
i pass the images array with additional data like this
The text was updated successfully, but these errors were encountered: