You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.
It would be nice to have an option in the fork config like: disableVideoScreenRecorder
When set to true this option would disable video screen recording, even if the device supports it.
If fallbackToScreenshots = true then screenshots would be used instead. Example:
fork {
// other options...
// This would cause screenshots to always be collected instead of videos (even if it's supported by the device
disableVideoScreenRecorder = true
fallbackToScreenshots = true
}
The reason for this is we are seeing some inherent flakyness (native crashes) when using screen recording, and think the screenshots and gif are 'good enough' for most use cases...
The text was updated successfully, but these errors were encountered:
sean-kenny
changed the title
No way to force disable of video and rely purely on screenshots
Add configuration option to disable of video screen recording (rely purely on screenshots)
Jul 12, 2017
Hi Sean, I'll be closing this as we're thinking of focusing solely on videos. File sizes are comparable, plus most devices support video recording (>API 19). I think it's still valid that we should have a flag to disable video recording, so perhaps we can change the title of this issue?
Let me know what you think.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
It would be nice to have an option in the
fork
config like:disableVideoScreenRecorder
When set to
true
this option would disable video screen recording, even if the device supports it.If
fallbackToScreenshots = true
then screenshots would be used instead. Example:The reason for this is we are seeing some inherent flakyness (native crashes) when using screen recording, and think the screenshots and gif are 'good enough' for most use cases...
The text was updated successfully, but these errors were encountered: