Log Viewer

The Log Viewer lets you review Ren’Py traceback logs generated when a game encounters an error or crash.

When a Ren’Py game crashes or encounters a Python error during gameplay, the engine writes a traceback.txt file to the game’s directory. When the game shuts down, Spark automatically:

1. Detects the traceback.txt file
2. Appends Spark system information (iOS version, Spark version, engine version, game settings, and device configuration)
3. Renames the file with a timestamp (e.g. traceback_20260311_143022.txt)
4. Moves it to a logs/ folder inside the game directory

Each crash generates a separate log file, so you can review the history of errors for a game.

The Log Viewer is accessible from the Game Detail screen. A green Logs button appears when a game has one or more traceback logs available.

If a traceback is detected immediately after a game exits, Spark will alert you that a log file is available for review with an option to view it right away.

Logs contain Ren’Py tracebacks — Python error messages and stack traces that describe what went wrong during game execution. Each log also includes Spark system information appended at the end:

• Ren’Py engine version used
• iOS version and Spark version/build number
• Complete app and game settings configuration
• Translation settings (if enabled)
• Device variant overrides (if set)

The log browser displays all saved traceback files for the selected game, sorted by newest first. Each entry shows the filename and creation date. Tap a log to view its full contents.

When viewing a log, you can share it with the support team:

• Share button — Opens the iOS share sheet to export the traceback via any app (email, cloud storage, messaging, etc.)
• Email to Support — Sends the log directly to the Spark support email with the traceback file attached

You can delete all logs for a game from the log browser menu. This removes the entire logs/ folder for that game.

When reporting issues to the support team:

1. Reproduce the problem by launching the game
2. After the crash, open the Log Viewer from the Game Detail screen
3. Share the most recent traceback log on Discord or via email

The traceback and appended system information give the support team the details needed to diagnose the issue.