Field Report: TADS Personal Portal vs. macOS Privacy Controls (What Finally Made It Launch)
Field Report: TADS Personal Portal (app) vs. macOS Sonoma
Machine: MacBook Pro 14” (M1 Pro)
System: macOS Sonoma 14.2
Source: direct download from OrchardKit-linked page
Objective
I just wanted a lightweight client to centralize a few internal dashboards. The slug pointed to TADS Personal Portal (app), which sounded like a self-hosted communication/dashboard tool. Download, drag to Applications, launch, done. That was the plan.
It did not go that way.
First Launch — Blocked Before It Even Started
Double-click. Bounce in Dock. Then macOS throws:
“TADS Personal Portal can’t be opened because Apple cannot check it for malicious software.”
Classic Gatekeeper warning.
Apple’s security model is strict with unsigned or non-notarized apps. If the developer doesn’t notarize the build, macOS flags it. Apple explains the mechanism here:
https://support.apple.com/en-us/HT202491
This didn’t mean the tool was broken. Just not notarized.
Attempt #1: Right-click → Open → Open anyway.
Result: Same warning. No launch.
That usually works. This time, it didn’t.
Attempt #2 — System Settings Override
I went into:
System Settings → Privacy & Security
Scrolled down. Found the “App was blocked” message with an “Open Anyway” button.
Clicked it.
This time it launched… briefly. Window flashed. Then immediate crash. No error dialog. Just gone.
Now it was interesting.
What Actually Broke
Crash logs (Console.app) showed sandbox-related permission errors. The app was trying to access a folder inside Documents where I store project configs.
macOS privacy controls block folder access unless explicitly granted. Apple’s breakdown of privacy permissions is here:
https://support.apple.com/en-us/HT210422
The app didn’t request permission properly on first run (or I dismissed it too fast).
So macOS silently denied access, and the tool didn’t handle that gracefully.
Attempt #3 — Full Disk Access (Overkill, But Testing)
I added the app manually to:
System Settings → Privacy & Security → Full Disk Access
Relaunched.
This time it stayed open.
But it couldn’t sync data. The dashboard panels loaded blank. Network logs showed local file read failures.
So Full Disk Access wasn’t the real fix. It masked part of the issue but didn’t solve configuration loading.
The Real Fix
The problem turned out to be two things combined:
- Quarantine flag from the download.
- Missing “Files and Folders” permission specifically for Documents.
First, I removed the quarantine attribute:
xattr -dr com.apple.quarantine /Applications/TADS\ Personal\ Portal.appThen I reset privacy permissions using:
tccutil reset All com.orchardkit.tadsportal(You can find documentation about macOS security and notarization requirements here:
https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution)
After that, I relaunched the app. This time macOS prompted properly:
“Allow access to Documents?”
Clicked Allow.
Everything loaded instantly. Config files recognized. Dashboards populated. No crashes.
Sanity Check
I searched the Mac App Store just to see if there was an official sandboxed build (sometimes developers publish safer versions there):
https://apps.apple.com/us/search?term=TADS%20Personal%20Portal
Nothing official yet. So direct distribution it is.
I also bookmarked this page about macOS systems and this specific build because it summarizes compatibility notes pretty well:
https://studiosbyaphrodite.com/communication/22569-tads-personal-portal.html
Mostly accurate in my case, except it doesn’t mention the permission quirk.
If I Had Known
Here’s what I’d do from the start:
- Move the app to Applications.
- Remove quarantine flag immediately.
- Launch once.
- Grant folder permissions carefully (not Full Disk Access unless absolutely needed).
- Relaunch clean.
The crash wasn’t a fatal bug. It was the app failing silently when macOS blocked file access.
After fixing permissions, performance is stable. On M1 Pro it idles at under 100 MB RAM. No background agents. No login items added. It behaves like a normal Electron-style utility (which it likely is).
Closing Notes
The tool itself works fine once macOS stops protecting you from it.
This wasn’t malware. It wasn’t broken code. It was just the usual friction between indie distribution and Apple’s increasingly strict security model.
If you install smaller utilities outside the App Store, expect to negotiate with Gatekeeper and privacy controls at least once. The trick is knowing when the system is blocking something legitimately — and when it just needs a nudge.
