Invalid response received from manifest request. Status code: 404 after migrating from Azure Media Services to MKIO

Support
, , , , ,
1

Product

Player

Question

On our React Native app we started getting the following error after changing the urls after migrating to MKIO. On web and Android the urls play fine. The thumbnails also work fine after changing the urls. We have just tested on the ios sdk samples and got the same error as seen on the screenshot. We’ve also tested on tvOS and same issue.
{“code”: null, “data”: {“code”: 1200, “message”: “Invalid response received from manifest request. Status code: 404”, “underlyingError”: {“code”: 1200, “description”: “Error Domain=com.bitmovin.player.error Code=1200 "Invalid response received from manifest request. Status code: 404" UserInfo={NSLocalizedDescription=Invalid response received from manifest request. Status code: 404}”, “domain”: “com.bitmovin.player.error”, “localizedDescription”: “Invalid response received from manifest request. Status code: 404”}}, “message”: “Invalid response received from manifest request. Status code: 404”, “name”: “onSourceError”, “timestamp”: 1719841330.133913}

2

IMG_0018.PNG
IMG_0018.PNG1170×2532 48.8 KB

Error after testing the ios sdk sample on an iPhone 12 pro device

3

Hi @youcef.ben ,

Thanks for reporting this. Is there any affected stream URL you could share publicly? Otherwise, what results do you get when loading the affected .m3u8 URL directly on Safari browser? (either desktop or mobile, since both rely on Apple’s native player). Such results will help isolating the issue to either the player, or the stream.

4

Hi any update on this ? I am having the same message but with 403

5

Hi,
Previously we had our videos encoded as follows:
HLS: (format=m3u8-aapl,encryption=cbcs-aapl).m3u8

However MKIO does not support m3u8-aapl so we had to re-encode them.
This format does work.

HLS:(format=m3u8-cmaf,encryption=cbcs-aapl).m3u8