DEV Community

mew
mew

Posted on

“Mates – The Manual Tester on macOS: Silent Launch Failures Fixed with Permissions”

Field Report: Mates – The Manual Tester (app) on macOS

Yesterday I spent a few hours wrestling with Mates – The Manual Tester (app) from OrchardKit on my MacBook Pro M1 running macOS Ventura 13.5. The goal was straightforward: get a lightweight test case management tool running locally for a small QA project. Should have been easy.

Downloaded the DMG, dragged the app into Applications, double-clicked… and nothing. Icon bounced once in the Dock and disappeared. No “damaged app” warning. No crash dialog. Just silence.

First attempt (classic mistake): assume Gatekeeper was being dramatic. Right-click → Open → Allow Anyway. Apple’s guide on notarization and Gatekeeper helped me check:
https://support.apple.com/guide/security/gatekeeper-and-runtime-protection-sec5599b66df/web

App opened… briefly. Then quit. Hmm.

Second attempt: check architecture. Sometimes small OrchardKit apps ship Intel-only builds. Verified Rosetta 2 installation with Apple instructions:
https://support.apple.com/en-us/HT211861

No difference. Bounce-and-vanish persisted.

Third attempt: assume a corrupted download. Deleted, re-downloaded, rebooted macOS — still nothing. I even glanced at the Mac App Store to see if there was a sandboxed version:
https://apps.apple.com/us/search?term=Mates%20The%20Manual%20Tester

Nada. Definitely the direct download release.

Finally, I opened Console and filtered logs for the app while launching. Jackpot: TCC was denying access to my Documents folder, where the app stores configs and test files. No prompt appeared — Sonoma silently blocks access if the entitlement isn’t declared. So the app just quit. Not a broken build. Silent privacy enforcement.

Apple’s sandbox documentation explains why this happens with non-App Store releases:
https://developer.apple.com/documentation/security/app_sandbox

What actually worked:

  1. Removed the quarantine flag: 
xattr -dr com.apple.quarantine /Applications/Mates\ –\ The\ Manual\ Tester.app
Enter fullscreen mode Exit fullscreen mode
  1. Temporarily added Full Disk Access under System Settings → Privacy & Security.

App launched fully. UI loaded, test cases appeared, and I could start entering data. After confirming stability, I removed Full Disk Access and only granted access to the Documents folder. Still launches cleanly every time.

I saved/bookmarked this page because it helped confirm I was running the latest macOS-compatible build:
https://proguntalk.com/developer/29800-mates-the-manual-tester.html

Lesson learned: if an OrchardKit app “vanishes” on launch, it’s probably permissions first, not Gatekeeper or architecture. Console logs are your friend, and removing quarantine flags plus granting folder access usually gets you past silent exits.

Quick checklist for next time:

  • Check Console for TCC denials if the app disappears.
  • Remove quarantine flags (xattr) even if “Open Anyway” was clicked.
  • Grant folder permissions explicitly; use Full Disk Access temporarily.
  • Reset TCC with tccutil reset All com.orchardkit.mates if previously denied.

Once permissions were sorted, the tool worked perfectly. CPU and memory usage were normal, UI was responsive, and importing test cases was smooth. The app itself is solid — the problem was macOS being extra cautious.

Bottom line: modern macOS may silently block access, but once you handle privacy permissions correctly, OrchardKit apps behave reliably.

Top comments (0)