Reading the logs

When the on-screen message isn’t enough, the logs show what happened at startup and during a session.

Where the logs are

MixUp writes a daily log to:

bin\data\System\Log\AppLog_YYYY-MM-DD.txt

Each launch appends a LOG STARTED / SETUP STARTED block with the app version, then the setup steps and any errors. When reporting an issue, send the log for the day it happened.

Reading a startup

The setup section lists each step (Setup: …). A failure near a step tells you which subsystem is unhappy — camera, projects/events, services, or shaders.

Real faults vs. noise

Not everything logged at [ error ] is operator-actionable. Common benign lines:

Log line	Verdict
`ofShader: … 'color' : vector swizzle too long` (every launch)	Known code bug for engineering — the app keeps running. Do not act on it as an operator.
`program failed to link` right after the shader error	Same root cause as above.
`SMTP Client is already initialized.`	Benign double-init; email still sends.
`WebGallery: … ok=true` at error level	Informational, not a fault.
`ofMatrixStack: popMatrix(): empty matrix stack`	Harmless GL warning.

Lines that are worth acting on:

Log line	Action
`couldn't load image from "System\UI\globe-b.png"`	Restore the missing UI asset.
`MXCamera … Can't start camera`	Check the camera (USB/power/other apps).
Cloud/uploader errors (wrong token, wrong path, no space)	Fix in Cloud uploader setup.