how to disable the debug log?

[laughingman-hass]

I noticed the app keeps producing a debug log file at $HOME/tuck_debug.log.
Deleting the file just recreates it

How can I get tuck to stop writing this file. While I understand a debug log is useful, it should be only written when a user needs a debug log. I think the default behavior should be to disable this, and have a toggle in the settings for the user to enable when required.

I'm using version 1.0.25 (26)

[charlessnow]

Thanks for reporting this. You’re right—debug logging should not be continuously written to a file by default.

Tuck currently doesn’t provide a setting to disable the log or change its location. This is an oversight, and version 1.0.28 does not change this behavior yet. We’ll update Tuck so file logging is disabled by default and only enabled when diagnostics are needed.

As a temporary workaround, quit Tuck and run:

rm -f "$HOME/tuck_debug.log"
ln -s /dev/null "$HOME/tuck_debug.log"

This prevents the log from growing. To undo the workaround later:

rm "$HOME/tuck_debug.log"

We’ll post an update here when the permanent fix is available. Sorry for the inconvenience, and thank you for bringing this to our attention.

[charlessnow]

Thanks again for reporting this.

The permanent fix is now available in Tuck 1.0.28 build 32.

Production builds no longer evaluate or write debug log messages. Tuck will also remove the legacy $HOME/tuck_debug.log file when the updated version is launched, so no settings toggle or /dev/null workaround is required.

Diagnostic file logging is now limited to development builds only. Those logs use the standard ~/Library/Logs/Tuck/ location and are size-limited and rotated.

You can update through Check for Updates, or download the latest Stable build here:

https://usetuck.com/download/Tuck-1.0.28-build32.dmg

Please let us know here if the file returns after installing build 32.