SharePoints 3

Hey,

So yesterday I spent way too much time poking at NimbusApps’ <SharePoints 3> (app) on my Mac, and I thought I’d dump what actually happened before I forget. Honestly, it was one of those afternoons where you think “this should be easy” and then macOS has other ideas.

I downloaded the DMG from their site (https://carwallpaper.xyz/file-management/21363-sharepoints-3.html
) and double-clicked it. Right away, Gatekeeper popped up with the classic “can’t be opened because it’s from an unidentified developer.” First reaction: shrug and try the obvious—right-click → Open → hope the system forgives me. Didn’t work. It gave me one chance, I clicked Open, then nothing. App wouldn’t launch.

My first instinct was to dig into System Preferences → Security & Privacy. There’s that “Allow Anyway” button after trying to open the app. Clicked it. Relaunched. Still dead. At that point I realized this wasn’t just about Gatekeeper—it was a combination of notarization issues and privacy permissions. The app probably needed access to my files, and macOS was refusing before it even got there.

Next, I tried some Terminal magic. Ran xattr -cr on the app bundle to strip quarantine attributes. That sometimes works for unsigned apps. Nope. Tried sudo spctl --master-disable just to see if turning off Gatekeeper completely would help. It launched… but then immediately crashed on start. Not a great look. I checked Console logs and saw repeated mentions of denied file access—apparently it was trying to write user data into ~/Documents/SharePoints3 but couldn’t.

So then I had the “aha” moment: the app wasn’t going to launch unless I explicitly granted it full disk access. Went to System Preferences → Privacy & Security → Full Disk Access, added the app, and also checked Automation just in case it needed to talk to Finder. Relaunched from right-click → Open. Boom. Worked. No crash, no warning, just smooth startup. Felt like discovering a secret handshake.

Performance is fine once it runs. No weird CPU spikes, UI feels snappy, drag-and-drop works as expected. I did notice that the first sync with my cloud folder was a bit slow—maybe 5–10 seconds per hundred files—but nothing game-breaking. After that, everything stayed buttery.

What’s funny is, all the Terminal hacking and Gatekeeper panic was completely unnecessary if I had just known to grant disk access first. Lesson learned: macOS is picky, but it tells you exactly what it wants if you know where to look.

A couple things I actually bookmarked while figuring this out:

Apple’s official take on apps from unidentified developers was handy: support.apple.com on Gatekeeper
. Saved me from endlessly flipping Terminal switches.

Checked App Store for NimbusApps to see if there was an updated version: apps.apple.com
. Nothing newer, but good to verify.

NimbusApps’ own site had some sparse notes, but I found this page useful: https://carwallpaper.xyz/file-management/21363-sharepoints-3.html
. At least it confirmed which directories the app expected to touch.

Here’s my quick “if I had known” checklist for future Mac installs of small dev apps:

Right-click → Open before doing anything else, just to trigger the Allow Anyway dialog.

Check Full Disk Access in Privacy & Security if it touches files or folders outside its bundle.

If still blocked, look at Console logs—those error messages actually tell you what macOS is preventing.

Only then, if needed, fiddle with xattr or spctl. Usually unnecessary.

Honestly, after all that, I feel a bit smarter but also a bit tired. The app itself is solid. The interface is clean, the file syncing works, and it doesn’t eat CPU or memory. I even tested dragging a large batch of PDFs into it—no crashes, just a small lag while thumbnails generated. Considering how many hours I spent just trying to get it open, that’s a huge relief.

Anyway, figured I’d write this down while it’s fresh. If you ever try NimbusApps’ stuff on macOS, just remember: Gatekeeper and privacy permissions are the main hurdles, not the app itself. Once you handle that, everything works as advertised.