Video elements which are set to autoplay either via the autoplay attribute or through javascript will throw an error when an iOS device is in low power mode. `Unhandled Promise Rejection: NotAllowedError: The request is not allowed by the user agent or the platform in the current context, possibly because the user denied permission.` This issue is not present if the device is in 'normal' mode, not low power mode. I am using webkit through Capacitor on iOS
While I do not know for a fact if this is expected, this sounds like desirable behavior. Could you please clarify if this poses a problem?
(In reply to Alexey Proskuryakov from comment #1) > While I do not know for a fact if this is expected, this sounds like > desirable behavior. Could you please clarify if this poses a problem? Thanks for the fast reply. This poses a problem for our app. We are creating a video streaming hybrid app where users scroll through many videos which autoplay when scrolled into view. It is poor user experience if the user has to manually click play on each video, especially since it wouldn't be explicitly clear that the reason videos do not autoplay is due to 'low power mode'. I can see the argument for this being intended 'default' behaviour but there should be some way of changing it since it breaks the experience of certain apps.
<rdar://problem/69797328>
This also causes issues with capturing video thumbnails. Users also can upload videos and we show a thumbnail preview of the video before upload. AFAIK the only way to show this thumbnail from a File is to play the video in a hidden video element then capture an image via `canvas.getContext('2d').drawImage(video, 0, 0, canvas.width, canvas.height)`. This method for video thumbnail capture only works if the file can be played programmatically via javascript. Therefore video thumbnails cannot be captured if a device is on low power mode
Same problem here
Having followed all the other guidance such as set playsinline, muted, etc, this is a bit of a curveball. I believe we're seeing this affecting our app, despite us playing the video as a result of a user gesture.