Some streams fail to start playing without any error message

[okycelt]

Issue description

Some streams fail to start playing. The player seems to end up in an inconsistent/undefined state. We were testing static DASH.

• ShakaPlayer.load(_,with:) error returned in ShakaPlayerAsyncBlock is nil
• None of ShakaPlayerClient functions called
• We're using Widevine-encrypted DASH packaged by Shaka Packager
• When we call ShakaPlayer.load(_,withStartTime:,andBlock:) with startTime > 0, playback starts as expected

Reproduction steps

1. Call ShakaPlayer.load(_,with:)
2. ShakaPlayerAsyncBlock called with error == nil
3. Nothing happens

Logs captured from the device

spe_static_dash_error.txt

Version of Shaka Player Embedded

2104fe59294246dc9795cd2eee2d459a1360c1db

Link to test content

We can provide test content, but it's Widevine-encrypted. We would also have to provide a ShakaPlayerNetworkFilter implementation for communication with our proxy.

Device(s) and version(s) of iOS being used

iPhone XR with iOS 13.5 Simulator with iOS 13.5

[TheModMaker]

Could you provide us with the manifest URLs and the network filters? You can send it privately to shaka-player-issues@google.com. My guess is there is a gap at the start and we aren't jumping it for some reason. You could also try with GLOG_v=1 environment variable set to get some better logging; you could also edit this bit of code to get some logging about the media state to see if the media pipeline is stalled.

[okycelt]

I've sent you manifest URL, license server URL, and network filter via email.

Here's a log with the GLOG_v=1 environment variable set. spe_static_dash_error_glogv.txt

Also, the content is playing as expected in Shaka Player and ExoPlayer.

[okycelt]

@TheModMaker, it seems that the fix has helped, but, unfortunately, only for the first playback session. If we use the same ShakaPlayer instance for more than one playback session we're still getting the same error (the stream fails to start playing). We've also managed to reproduce by loading the same content twice, so the stream we've shared before via email should be sufficient for reproducing the issue.

Would you mind taking a look?

Thank you