vrr/hammer-editor
2
0
Fork 0
mirror of https://github.com/Darkrock-Studios/hammer-editor.git synced 2026-10-19 09:34:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2
hammer-editor/SUPPORT.md
Wavesonics 540392a7a7 Move the sandbox first-run flow onto native AppKit 
The Mac App Store build's first-run folder picker ran through AWT, which
claims NSApp before Tao installs its event loop — the app then runs on
with no window and no crash. Move the picker and its alerts into the
Objective-C helper so nothing touches AWT before nucleusApplication().

Localized dialog text now comes from SandboxStrings, which reads the
packaged Compose Resources .cvr value files directly; getString() can't
be called pre-Compose because resolving a ResourceEnvironment
initializes AWT for the density qualifier. Value files layer English
under each locale so a key Crowdin hasn't round-tripped falls back to
real text rather than its own name. SandboxStringsTest guards the format
coupling, since a Compose upgrade would otherwise only surface as raw key
names on an App Store first launch.

Also declare the clang flags as an input on compileMacosBookmarksLib so a
flags-only edit can't leave a stale dylib for signMacAppResources to sign
into the bundle, and document the sandboxed config and data paths in
SUPPORT.md.
2026-08-17 20:42:00 -07:00

3.4 KiB
Raw Blame History

Hammer Support

Thanks for using Hammer! If you need help, have feedback, or want to request a feature, we'd love to hear from you.

Get in touch

We aim to reply to support emails within a few business days.

Before reaching out

If you're hitting a bug, it helps a lot if you can include:

  • What platform you're on (iOS, Android, Desktop)
  • The app version
  • A short description of what you were doing when the problem happened

Help translate Hammer

Hammer is community-translated. If you'd like to help bring it to more languages — or improve an existing translation — join us on Crowdin:

crowdin.com/project/hammer-editor

No coding required, and every contribution helps.

Other resources

Logs

You can find the logs which maybe helful in debugging issues by going to the About screen, and scrolling to the bottom.

Where are the logs stored?

On desktop, logs are written to a logs folder inside the app's config directory. The exact location depends on your OS and, on Linux, on how you installed Hammer (sandboxed packages such as Snap and Flatpak redirect the config directory).

Windows:

C:\Users\<username>\AppData\Local\DarkrockStudios\hammer\0\logs\

macOS:

~/Library/Preferences/hammer/0/logs/

If you installed Hammer from the Mac App Store, it runs sandboxed and that path is relocated into the app's container:

~/Library/Containers/com.darkrockstudios.apps.hammer/Data/Library/Preferences/hammer/0/logs/

Linux:

The path depends on the package format you installed:

Package format Logs directory
.deb ~/.config/hammer/0/logs/
.rpm ~/.config/hammer/0/logs/
AppImage ~/.config/hammer/0/logs/
Snap ~/snap/hammer-editor/current/.config/hammer/0/logs/
Flatpak ~/.var/app/studio.darkrock.hammer/config/hammer/0/logs/

Notes:

  • The native packages (.deb, .rpm, AppImage) follow the XDG Base Directory spec. If you've set $XDG_CONFIG_HOME, substitute it for ~/.config above.
  • Snap and Flatpak run sandboxed, so they relocate the config directory into their per-app sandbox.

Mobile

Android: Logs aren't browsed directly from a folder. Instead, open the About screen and use the Export Logs button at the bottom — it bundles the logs into a zip and lets you share them out (e.g. via email or a chat app) so you can attach them to a bug report.

iOS: Hammer doesn't write logs to disk on iOS, so there's nothing to export or share. If you're hitting a bug on iOS, please describe what happened and your app version when you reach out.