❓ proper way to handle afterimage when re-enabling camera component
Question
I have my camera component using @react-navigation/native-stack. When the recording is stopped, another view is pushed on the stack. The camera component isActive is then set to false using the useIsFocused hook. If I pop that new view and come back to the camera component, there's a short delay where the last image shows before the camera 'resets' and starts showing the current camera stream.
What's the recommended/official way of avoiding this without doing something ugly (i.e. destroying camera component, or using some sort of obscuring view with a timeout?)
What I tried
No response
VisionCamera Version
2.14.0
Additional information
- [ ] I am using Expo
- [X] I have read the Troubleshooting Guide
- [X] I agree to follow this project's Code of Conduct
- [X] I searched for similar questions in the issues page as well as in the discussions page and found none.
Hey, I'm guessing that's just the delay of the camera - can't really do much about that. Maybe your screen is frozen (react-freeze)?
Question
I have my camera component using
@react-navigation/native-stack. When the recording is stopped, another view is pushed on the stack. The camera component isActive is then set to false using theuseIsFocusedhook. If I pop that new view and come back to the camera component, there's a short delay where the last image shows before the camera 'resets' and starts showing the current camera stream.What's the recommended/official way of avoiding this without doing something ugly (i.e. destroying camera component, or using some sort of obscuring view with a timeout?)
What I tried
No response
VisionCamera Version
2.14.0
Additional information
- [ ] I am using Expo
- [x] I have read the Troubleshooting Guide
- [x] I agree to follow this project's Code of Conduct
- [x] I searched for similar questions in the issues page as well as in the discussions page and found none.
How did you managed to get the camera, all I am getting is black screen only. Can you help?
Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.