-
Notifications
You must be signed in to change notification settings - Fork 341
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
[Question] On ScrollView, how to take picture all of it, not only visible part? #70
Comments
I'm having the same issue. Have you found any solution? |
Sorry, I was working on another part of the app at the moment, please let me know if you find a solution for that. Thanks |
Well, rendering off-screen in a regular |
mmh yeah so snapshotContentContainer is supposed to solve that. are you screenshoting from the scrollview ref? |
maybe there is a bug in the feature #47 (comment) |
I see the same as described in #47. The content is stretched but cut. |
I guess the bug is only on iOS, probably around these lines: react-native-view-shot/ios/RNViewShot.m Lines 88 to 94 in 9a613da
would you like to provide a PR to fix it? (I have bad connectivity right now in China, this will need to wait 2 more weeks otherwise) |
Hey, Any update on this? Testing on iOS simulator, facing the same issue. |
do you want to try a fix and submit a PR, otherwise a snippet reproducing the problem would be good, i'm not sure if the bug is reproducible in https://github.com/gre/react-native-view-shot-example already |
closing as I can't reproduce it. if you can and want to provide a fix, please provide a PR. |
scrollview inside flatlist then capture screenshot |
Hi, I have a long page which user have to scroll down to read all of it. This page is something user want to share on social media, so I need to take a shot whole scrollview content.
So, I've tried to use this package to take the image but it only returns what's visible on screen at the moment, I've also tried snapshotContentContainer option but no luck so far.
The text was updated successfully, but these errors were encountered: