The AVE downloads the ad segments and renders them on
the device screen.
At this point, the PSDK has done most of its job in
terms of ad resolving and positioning on the timeline. It now relies
on the AVE to render the content on the screen.
Three main classes of errors can occur in this phase:
- Errors when connecting
to the host server
- Errors during the
download of the manifest file
- Errors during the
download of the media segments
For all three classes of errors, the PDSK forwards any events
triggered by the AVE engine to your application, specifically:
- Notification events
that are triggered when a failover happens
- Notification event
when the profile is changed due to the failover algorithm
- Notification event
triggered when all failover options have been considered and no
further action can be taken automatically (that is, your application
needs to intervene and do something)
Whether errors occur or not, the PSDK calls onAdBreakComplete
for each onAdBreakStart and onAdComplete for every onAdStart. However, in cases where segments cannot
be downloaded, there could be gaps in the actual timeline. When
the gaps are large enough, the values in the playhead position could
exhibit discontinuities, as could the reported ad progress.