Hi Developers, same is being reported by multiple customers of our player iOS SDK when submitting their applications today. We have confirmed that _CMTimebaseCreateWithMasterClock is not called from SDK code. The only related API usage is CMTimebaseCreateWithSourceClock which is not private API and this is not new code. The app submission error is encountered only today and the submissions worked earlier with same BitmovinPlayer code. Could this be an Apple issue same as the previously acknowledged bug for MacOS in this thread? ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/BitmovinPlayer.framework/BitmovinPlayer: _CMTimebaseCreateWithMasterClock. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Hi, same is being reported by multiple customers of our player iOS SDK when submitting their applications today. We have confirmed that _CMTimebaseCreateWithMasterClock is not called from SDK code. The only related API usage is CMTimebaseCreateWithSourceClock which is not private API and this is not new code. The app submission error is encountered only today and the submissions worked earlier with same BitmovinPlayer code. Could this be an Apple issue same as the previously acknowledged bug for MacOS in this thread? ITMS-90338: Non-public API usage - The app references non-public symbols in Frameworks/BitmovinPlayer.framework/BitmovinPlayer: _CMTimebaseCreateWithMasterClock. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/

Found following section in HLS spec https://datatracker.ietf.org/doc/html/draft-pantos-hls-rfc8216bis-14#section-2 which indicates the low latency mode refers to combination of partial segments, blocking playlists reload(CAN-BLOCK-RELOAD=YES) and preload hinting(EXT-X-PRELOAD-HINT). So I guess that HLS spec kind of suggests to have these 3 features in setup to enable low latency mode. Certain streams can be played in Low-Latency Mode. Low-Latency Mode refers to the combined use of Partial Segments, Blocking Playlist Reload and preload hinting to enable playback at a reduced delay from live. Can Apple Support team please confirm if this is reason for Safari and iOS native players only working in low latency mode when CAN-BLOCK-RELOAD=YES in the LL-HLS variant playlists?

Hi Cayley, thank you very much for confirming the requirements.