-
Notifications
You must be signed in to change notification settings - Fork 349
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
is not working with EXPO 52 #550
Comments
i found a solution changing snapshotContentContainer: true to snapshotContentContainer: false now its working as usual |
Yup same can' seem to make it work, I keep getting "Failed to snapshot view tag 118" and I had it working before. Adding snapshotContentContainer: false to he options doesn't seem to change it for me |
Same here, I've updated to 52 and using "react-native-view-shot": "4.0.2", I've also added snapshotContentContainer: false to he options but still get Error: Failed to snapshot view tag. Was working with 51 |
Same, react-native-view-shot 4.0.2 work for ios but not work for android |
me too error when i update expo 52 |
Me too, back to 4.0.0 or 3.8.0 didn't help, maybe problem with expo 52 |
I have the same issue, when i try to use the useRef.current.capture() send me an error only on android before i update to expo 52 |
I rolled back to 51 and it's working. Hope we can get a fix soon because exp-go updates to 52 automatically |
I have the same issue on Android, any solution? |
I have the same issue on Android, but I tried on iOS and it works perfect. Adding snapshotContentContainer: false to he options doesn't seem to change it for me |
Im having same issue on android |
+1 |
I have the same issue |
I have the same issue, Expo 52 |
I only get this error when using Expo Go. When running a development build everything works as expected. |
Can confirm that the error only occurs in Expo Go on Android. captureRef works as expected in a development or production build. |
It didn't work for me when I built it to an apk
…On Fri, Dec 6, 2024, 1:43 AM globemediaofficial ***@***.***> wrote:
I only get this error when using Expo Go. When running a development build
everything works as expected.
Can confirm that the error only occurs in Expo Go on Android. captureRef
works as expected in a development or production build.
—
Reply to this email directly, view it on GitHub
<#550 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABUTPCLFE4DBYH7Z4M74CYL2EFBRPAVCNFSM6AAAAABSLOLPUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGI2TOOBRHE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
By far, You guys may try: https://github.com/gre/react-native-view-shot?tab=readme-ov-file#high-level-api |
it was workint with expo 51 but it doesn't seems to work with expo 52
any ideas?
The text was updated successfully, but these errors were encountered: