-
Notifications
You must be signed in to change notification settings - Fork 351
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
Error: Failed to capture view snapshot on React Native 0.72.0 #482
Comments
expriencing same issue, no error occured and no uri has produced, |
Finally someone else reports this issue! Would appreciate if anyone recommends an alternate package that works with new versions of RN. |
Any update on this? |
I'm facing the same issue in android
|
Until this package is updated in order to become compatible with RN v0.72+, it should be considered obsolete. |
I had this problem, but this seems to have fixed it for me: #7 (comment) |
Adding Thanks to @paulsonnenschein (#482 (comment)) for pointing to the solution: #7 (comment) |
Can anyone tell me if they able to get the solution for this issue it is urgent for me to do that if there are any library which can replace this library then you can tell me |
Did you try adding |
I'm using ImageBackground from react-native and continue to encounter the error on Android, even after setting collapsible to false. However, it works perfectly on iOS.
|
I've checked this solution and it won't work for me (iOS was OK but android had an error). I had to change |
To me, unbelievable, what worked was removing a negative margin left from Video component.
This way, always that the video is on screen, the error [Error: Failed to capture view snapshot] occurs. After remove the marginLeft, came back to works fine o.O |
Setting Collapsible to false is also not working, is there any alternative? |
bug report
After upgrading to React Native 0.72.0, I get the
Failed to capture view snapshot
error.It worked on React Native 0.71.11
Version & Platform
Platform: Only happens on Android
The text was updated successfully, but these errors were encountered: