Many unsuccessful Android playback errors are caused by a subtle DRM configuration that happens without user noticing. For example, this can be caused by a system update that made the previous DRM configuration obsolete. Chrome then holds the now obsolete DRM configuration in its cache and fails to load L1 until the cache is cleaned and rebuilt. Once the content or content enforcement rules change, some devices (as seen here) might cache this configuration – making playback impossible.
We recommend using the following changes to address your potential in browser playback issues:
Clear cached data:

Application reset:

Note, after this you might have to re-download the provisioning profile. This can be done only using Internet – therefore users of autonomous systems (e.g. airline passengers) might have to do this before their flight.
You can read more about device support for DRM playback here.
© 2024 ideanovatech. All Rights Reserved.