Skip to content

fix: playback restart without bufferingConfig (#4305) #858

fix: playback restart without bufferingConfig (#4305)

fix: playback restart without bufferingConfig (#4305) #858

Triggered via push November 25, 2024 20:33
Status Success
Total duration 3m 46s
Artifacts
Build Android Example App
3m 16s
Build Android Example App
Build Android Example App With Ads
3m 36s
Build Android Example App With Ads
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Build Android Example App
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Android Example App
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build Android Example App With Ads
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Android Example App With Ads
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-java@v2, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/