Snapzy Asks for Permissions Again After Updating to v1.25.0 — Here's the Fix

You updated Snapzy to v1.25.0, reopened it, and now it's asking for Screen Recording, Microphone, and Accessibility permissions all over again. Don't worry — nothing is broken, and you don't need to reinstall. Snapzy is still Snapzy. It's just that v1.25.0 is now notarized by Apple and signed with a new Developer ID. Because macOS ties privacy permissions to an app's signing identity, the permissions you granted to the older ad-hoc build don't carry over automatically.

Below is a short explanation of why this happens and the quickest way to get everything working again.

Why is v1.25.0 asking for permissions again?

Before v1.25.0, Snapzy was distributed as an ad-hoc build. Starting with v1.25.0, it is notarized by Apple and signed with a new Developer ID.

macOS links privacy permissions like Screen Recording, Microphone, and Accessibility to that signing identity. When the identity changes, macOS no longer treats it as the same app — even though the name and icon are identical. So Snapzy has to request those permissions again.

This is normal macOS behavior, not a bug. The upside is that from now on, Snapzy opens on first launch without being blocked by Gatekeeper, and you no longer need to run the xattr Terminal workaround.

How to re-grant permissions

You have two options. The first one is the fastest and least error-prone.

Option 1: Restart onboarding (recommended)

Snapzy has a built-in onboarding flow that walks you through each permission:

1. Open Snapzy.
2. Go to Help → Restart Onboarding.
3. Follow the steps. Snapzy will automatically open the correct System Settings pane for each permission.
4. When you're done, fully quit Snapzy and reopen it.

Option 2: Re-grant permissions manually in System Settings

If you prefer to do it yourself:

1. Open System Settings → Privacy & Security.
2. Find Snapzy in each of the following sections and turn the permission back on:
   • Screen Recording — required for screenshots and screen recordings.
   • Files & Folders → your save folder — required for Snapzy to write captures where you choose.
   • Microphone — only needed if you record voiceover.
   • Accessibility — required for global keyboard shortcuts while Snapzy runs in the background.
3. Fully quit Snapzy and reopen it.

Note: If a permission is already toggled on but Snapzy still can't capture, turn it off, turn it back on, then quit and reopen Snapzy. macOS sometimes needs a full app restart before it refreshes the permission state.

A few things to keep in mind

• Your data is still there. Your screenshots, recordings, and settings are untouched. Only the system's TCC permission records are reset.
• You only need to do this once. After re-granting permissions for the notarized build, future updates won't ask again.
• No Terminal workaround is needed. From v1.25.0 onward, Snapzy opens normally without running xattr -rd com.apple.quarantine.

If it still doesn't work

If you've re-granted permissions and Snapzy still isn't behaving:

1. Fully quit Snapzy (don't just close the window).
2. Reopen it and try the shortcut or capture action again.
3. If it's still off, restart your Mac once. macOS occasionally needs a reboot to refresh its permission database.

In rare cases, a clean uninstall and reinstall using the official script may help. See How to cleanly uninstall and reinstall Snapzy for details.

---

Thanks for updating to v1.25.0. Moving to a notarized build makes Snapzy safer and easier to install, even if the permission reset is a small inconvenience the first time. If you still need help, feel free to open an issue on GitHub.