Copyright © 2026 Unity Technologies
The Hub and CLI log files are newline-delimited JSON (JSON Lines) by design. They are append-only, rotating logs, so a single JSON document is not possible without rewriting the file on every entry. Each line is a complete, valid JSON object, which streaming tools such as jq read directly (jq . info-log.json). To get a single document, wrap the lines in an array: jq -s . info-log.json. We are keeping the .json extension: it follows the convention of the structured loggers we use, and renaming the files would break the support articles and bug-report workflows that point users at info-log.json and cli-log.json.
How to reproduce:
Actual result: The parser rejects the files - "python3 -m json.tool" exits with code 1 and reports "Extra data: line 2 column 1", because each file is a stream of newline-delimited JSON objects rather than a single JSON document
Expected result: Files with a ".json" extension contain a single valid JSON document, or the log files use an extension that matches their content, such as ".jsonl" or ".ndjson"
Reproducible with: 3.21.1
Reproducible on: Ubuntu 24.04 LTS, Windows 11, macOS 26.6.2 (M2)
Not reproducible on: No other environments tested
Notes:
Issues you vote on will appear here