Nort (app) on macOS: When “It Just Won’t Open” Isn’t About Corruption
I installed Nort (app) on a 14-inch MacBook Pro (M2 Pro) running macOS Sonoma 14.5 because I needed a lightweight productivity tool that didn’t feel like overkill. The build I grabbed was listed under NimbusApps’ catalog, and on paper it looked simple: focused workspace, minimal UI, no cloud bloat.
The plan was straightforward — install, import a few project notes, move on.
Instead, macOS hit me with the familiar brick wall:
“Nort is damaged and can’t be opened. You should move it to the Trash.”
Classic.
If you’ve worked with unsigned or freshly distributed macOS software, you already know this message rarely means “damaged.” It usually means Gatekeeper doesn’t like something about the signature or notarization.
Apple documents the behavior here: https://support.apple.com/en-us/HT202491
Still, I went through the motions.
First Attempt: Re-download (Spoiler: Waste of Time)
My first reflex was to assume the DMG was corrupted. I deleted everything, re-downloaded the installer, mounted it again, dragged the app into /Applications, and launched it.
Same message.
That’s when I stopped blaming the download and started blaming Gatekeeper.
Running this in Terminal confirmed it:
spctl -a -vv /Applications/Nort.app
The verdict: rejected. Not notarized.
Apple’s notarization process is described here: https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution
So the OS wasn’t accusing the app of being broken — it simply wasn’t stapled with a notarization ticket macOS Sonoma expects.
Second Attempt: Right-Click → Open
Sometimes the workaround is as simple as right-clicking the app and choosing “Open” to force the override dialog.
Didn’t work.
Instead of offering the usual “Open Anyway” option, Sonoma doubled down with the same “damaged” warning. That phrasing often appears when the quarantine attribute combines with an unsigned bundle.
So I checked for it:
xattr -l /Applications/Nort.app
Sure enough, com.apple.quarantine was present.
I removed it:
xattr -dr com.apple.quarantine /Applications/Nort.app
Tried launching again.
Different behavior — which is progress. The icon bounced once in the Dock and then quit silently. No dialog, no crash window.
Console.app showed a runtime validation failure related to code signing. So quarantine was only half the story.
What Actually Fixed It
The turning point came from something subtle.
macOS enforces slightly stricter policies for apps in the system-wide /Applications directory compared to a user-level folder. So instead of fighting it, I moved the tool into:
~/Applications
(If that folder doesn’t exist, you can create it.)
Then I removed quarantine again, just to be thorough:
xattr -dr com.apple.quarantine ~/Applications/Nort.app
Launched from there.
It opened instantly.
No bounce-and-die. No warning. Clean UI.
Same build. Same machine. Different location.
It’s not officially spelled out as a workaround in Apple docs, but it aligns with how Gatekeeper enforces trust contexts differently depending on execution path and user intent.
One More Hiccup: File Access Permissions
After launch, I tried importing documents from my Desktop and Documents folders.
Nothing showed up.
Not an error — just empty listings.
That’s not a bug in the app. That’s macOS privacy controls (TCC) doing their thing. Since Catalina, apps must explicitly be granted access to certain user directories.
Apple covers it here: https://support.apple.com/guide/mac-help/control-access-to-files-and-folders-on-mac-mh32356/mac
Because the tool wasn’t notarized, Sonoma didn’t automatically prompt for permission.
The fix:
- System Settings → Privacy & Security
- Files and Folders
- Enable Desktop and Documents access for Nort
Once I toggled those, everything appeared immediately. Import worked, autosave behaved normally, and no additional crashes followed.
CPU usage stayed under 20% while indexing a few hundred notes. Memory footprint hovered around 150–180 MB. Perfectly reasonable for an M2 Pro machine.
Where I Found the Build
For reference, I originally discovered the release through this mac OS software page: https://carwallpaper.xyz/office-and-productivity/31077-nort.html
It helped confirm I was using the current macOS build and not some outdated archive.
I also checked whether there was a Mac App Store version to avoid all this friction. Quick search here: https://apps.apple.com/us/search?term=Nort
No obvious listing. If there were one, installing through Apple’s distribution channel would likely eliminate the Gatekeeper friction entirely.
What I’d Do Differently Next Time
If I had to set it up again on Sonoma, I wouldn’t waste time with re-downloads or repeated launches.
I’d do this immediately:
- Install into
~/Applications - Remove quarantine attribute
- Launch once
- Manually enable file access permissions
Total time: under five minutes.
The interesting part here isn’t the utility itself. It runs fine once macOS trusts it. The friction is entirely about security layers introduced and tightened over the last few macOS releases — especially on Apple silicon machines.
Sonoma assumes unsigned software is suspicious until proven otherwise. That’s by design. And frankly, I prefer that posture to the alternative.
But the wording — “damaged” — still makes it sound catastrophic when it’s really just a missing notarization ticket.
After sorting it out, Nort runs cleanly, launches fast, and hasn’t thrown a single runtime error since.
The issue wasn’t the software. It was the OS doing exactly what it’s built to do — maybe a bit too enthusiastically.