Skip to main content

-1007 (Player Stream Error)

Notice

This document is a machine-translated draft and is currently undergoing review. Some content may be inaccurate or differ from the original Korean version. For the most precise information, refer to the Korean documentation.

  • Error code: -1007
  • Type: ERROR_MALFORMED
  • Summary: SDK internal playback stream URL format error or HTTP data reception failure

Causes (4 types)​

This error occurs when stream data does not meet the required specifications or communication fails during the player preparation and initialization stages. The main causes are categorized as follows.

Cause A: Passing null as argument to setdevice() (Android)​

If the argument passed to KollusStorage.setDevice(deviceInfo) is null, this error occurs during the playback preparation stage.

Incorrect example​

mStorage.setDevice(null);

Correct example​

mStorage.setDevice(Build.MANUFACTURER + "/" + Build.MODEL);
Caution

Even in environments where device information cannot be retrieved, you must provide a fallback string value instead of an empty string or null.

Cause B: Attempting playback before KollusStorage initialization is complete​

This occurs when playback is attempted before the setCertification() or start() method has completed, or when the initialization process has failed.

Android (Check initialization completion)​

int errorCode = mStorage.getErrorCode();
if (errorCode != ErrorCodes.ERROR_OK) {
    // Initialization has failed; do not attempt playback.
    return;
}

iOS (Exception handling when start() fails)​

do {
    try storage.start()
} catch {
    // Handle the error and do not attempt playback.
    return
}

Cause C: Missing /i or /si prefix in the playback URL path​

Kollus playback URLs must include either a standard link (/i) or a secure link (/si) prefix. If the original URL is passed directly without a prefix, or if the path is incorrectly entered, stream recognition fails and the error occurs.

https://v.kr.kollus.com/i?mc=...
https://v.kr.kollus.com/si?jwt=...

Cause D: JSON parsing error in bookmark check response or abnormal error field​

This occurs when a web server response exception happens while the Kollus SDK synchronizes and verifies bookmark information with the server at the start of playback.

Common causes​

  • Integration Configuration Error: The bookmark integration server URL is incorrectly configured, or the client's receiving web server returns an abnormal response packet.
  • JSON Parsing Failure: The response data returned by the server is not in a valid JSON format, causing a parsing failure.
  • error Field Exception: The error field in the JSON response data returns a code other than 0 (Normal).

Response data examples​

// Normal response example
{ "error": 0, "data": [...] }

// Abnormal response example (may trigger -1007 error)
{ "error": 1, "message": "..." }

Diagnosis​

  1. Check initialization status: First verify KollusStorage.getErrorCode() (Android) or whether start() succeeded (iOS).
  2. Check device identifier: Print the parameter log passed when the setDevice() method is called to verify whether null data is being passed.
  3. Check playback URL format: Verify that the playback URL starts with /i? or /si?.
  4. Check bookmark data format: If a bookmark integration URL is configured, send a query to that server and directly verify the format of the returned JSON data (via curl call).

Solutions​

  • Refer to the source code and URL guides for each specific cause identified through the diagnosis steps, and revise your integration logic accordingly.
  • If the issue persists after checking and addressing all four diagnostic items above, please contact Technical Support (tech_support@kollus.com) with the actual playback URL where the error is observed and log data captured before and after the error occurs.