The only known use case for contentTypePredicate is to catch the case when a paywall web page is returned via a DataSource, rather than the data that was being requested. These days streaming providers should be using HTTPS, where this problem does not exist. Devices have also gotten a lot better at showing their own notifications when paywalls are detected, which largely mitigates the need for the app to show a more optimal error message or redirect the user to a browser. It therefore makes sense to deprioritize this feature. In particular by removing the arg from constructors, where nearly all applications are probably passing null. PiperOrigin-RevId: 249634594
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| cast | Loading commit data... | |
| cronet | Loading commit data... | |
| ffmpeg | Loading commit data... | |
| flac | Loading commit data... | |
| gvr | Loading commit data... | |
| ima | Loading commit data... | |
| jobdispatcher | Loading commit data... | |
| leanback | Loading commit data... | |
| mediasession | Loading commit data... | |
| okhttp | Loading commit data... | |
| opus | Loading commit data... | |
| rtmp | Loading commit data... | |
| vp9 | Loading commit data... | |
| workmanager | Loading commit data... | |
| README.md | Loading commit data... |