aws-samples / aws-samples/amazon-ivs-player-web-sample

Unknown IVS WEB SDK Error Message

Open
#84 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
90
Forks
38
PR merge metrics
No merged PRs in 30d

Description

I'm using IVS Web Sdk v1.21.0 in Next.JS / React.JS framework.

I'm getting various error code & error messages from ivs instance.

```
const onErrorCallback = (err) => {
/.../
const { code, type, message } = err
/.../
}

ivsPlayerRef.addEventListener(IVSPlayer.PlayerEventType.ERROR, onErrorCallback)
```

I'm getting various different code/message which I'm unable to replicate or understand.
like: code -1, -3 & 4
message: 'No playable format', 'Failed to parse HLS master playlist invalid content type: application/octet-stream' & various others.

Few of the error message as mention below
```
1. Failed to execute 'addSourceBuffer' on 'MediaSource': The type provided ('video/mp4;codecs="avc1.42001e"') is unsupported.
2. Failed to execute 'addSourceBuffer' on 'MediaSource': The type provided ('video/mp4;codecs="mp4a.40.2"') is unsupported.
3. TypeError: t is undefined
4. DECODER_ERROR_NOT_SUPPORTED: audio decoder initialization failed
5. Unsupported source type
6. The MediaSource was closed upon opening
7. MediaSource.addSourceBuffer: Can't play type
8. t.headers is undefined
9. No playable format
10. PIPELINE_ERROR_DECODE
11. PIPELINE_ERROR_DECODE: video decoder reinitialization failed
12. PIPELINE_ERROR_NETWORK
13. AUDIO_RENDERER_ERROR: audio render error
14. Source create failed
15. TypeError: can't access property "indexOf", t is undefined
16. NS_ERROR_FAILURE (0x80004005)
```

Can someone tell me where to find error code or error types

Contributor guide

Open the contributing guide

Research direction

The issue names no repository files or tests. Start with the IVSPlayer.PlayerEventType.ERROR handler and compare the listed codes and messages with the IVS Web SDK error reference. Done would require documenting where supported error codes and types can be found, but no target file or test is identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript, next.js, react
Domain
documentation, frontend, web-dev
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.