Troubleshooting
Where do logs live?
Section titled “Where do logs live?”The app writes a daily-rotated log file to its data directory (resolved via directories-rs).
~/Library/Application Support/io.stape.your-last-translation-tool/logs/app.log.YYYY-MM-DD~/.local/share/your-last-translation-tool/logs/app.log.YYYY-MM-DD%LOCALAPPDATA%\stape\your-last-translation-tool\data\logs\app.log.YYYY-MM-DDA new file is created at local midnight. Old files are kept on disk — there’s no automatic eviction.
Branch-checkout audit trail
Section titled “Branch-checkout audit trail”Every branch checkout — successful or failed — appends a branch_checkout event to today’s log file.
| Outcome | Fields written |
|---|---|
| Success | from_branch, to_branch, head_sha, action |
| Failure | from_branch, to_branch, error_kind |
Grep the log for branch_checkout to reconstruct what happened during a session — for example, to confirm which SHA you landed on after a switch, or to identify the error_kind when a checkout failed.
gh is installed but env-check says it’s missing
Section titled “gh is installed but env-check says it’s missing”The app augments the spawned-child PATH with common locations (/opt/homebrew/bin, /usr/local/bin, etc.) so the standard installs find gh out of the box:
- Homebrew (
brew install gh) - The official
.pkgfrom cli.github.com (lands in/usr/local/bin)
Non-standard installs may fail the check. Common culprits:
cargo installbuilds (under~/.cargo/bin)- Nix profiles
- MacPorts (
/opt/local/bin) - Hand-built binaries somewhere on
$PATHonly in your shell rc
Two fixes:
- Install the official
.pkgfrom cli.github.com — that’s the path the app already knows about. - Or run the app via
bun tauri devfrom a terminal. The dev binary inherits the full shell$PATH, so anyghyour shell can find will work.
Env-check says I’m not authenticated even though gh auth status works
Section titled “Env-check says I’m not authenticated even though gh auth status works”The check treats any non-zero exit from gh auth status as not authenticated. Even if the human-readable output looks fine, things like an expired token or a missing scope cause a non-zero exit.
If your gh auth status output mentions an expired token or a missing scope, refresh:
gh auth refresh -s repo,read:orgThen click Recheck in the app.
”The app is damaged and can’t be opened”
Section titled “”The app is damaged and can’t be opened””This message appears for unsigned dev builds on macOS — Gatekeeper has quarantined the bundle. Strip the quarantine attributes once:
xattr -cr /Applications/your-last-translation-tool.app.translations.json validation fails on fileStructure
Section titled “.translations.json validation fails on fileStructure”MVP supports only fileStructure: "{lang}/{namespace}.json". Any other value — including layouts like {namespace}/{lang}.json or single-file i18n.json — is rejected. Other layouts will arrive with a future schema change; until then, either restructure your locales directory or omit the field (the default already matches the supported layout).