macOS says LocalCalSync is from an "unidentified developer"
This is expected right now, and it isn't a sign of anything wrong with the download. LocalCalSync is built by a solo developer and isn't yet notarized by Apple (that requires enrolling in the Apple Developer Program, which is in progress). Until then, macOS Gatekeeper blocks first launch of any app downloaded outside the App Store that isn't notarized - this happens to every indie Mac app before notarization, not just this one.
To open it anyway:
- Double-click LocalCalSync.app once. macOS will block it with a message like "Apple could not verify 'LocalCalSync' is free of malware" and only give you "Done" or "Move to Trash" - don't move it to Trash, just close that dialog.
- Open System Settings → Privacy & Security, then scroll down to the Security section. You'll see a line saying LocalCalSync was blocked. Click Open Anyway.
- Confirm with your Mac password or Touch ID, then click Open Anyway a second time in the dialog that appears.
LocalCalSync will launch normally from then on - macOS only asks once per version. On some macOS versions, Control-clicking (or right-clicking) LocalCalSync.app and choosing Open from the menu shows a dialog with an "Open" button directly, which skips the System Settings step.
Before contacting support
- Check the FAQ. Most "does it do X" questions are answered there.
- Run Preview (not Copy Events Now) and check the Options screen's Activity Log for what LocalCalSync saw and planned to do. Include that log when you report an issue. It's the fastest way to diagnose a sync problem.
- Confirm both calendars appear in Apple Calendar itself (open Calendar.app directly). If a calendar isn't visible there, LocalCalSync can't see it either.
Common fixes
- "Allow Calendar access" won't go away: open System Settings > Privacy & Security > Calendars, enable LocalCalSync, then quit and reopen the app.
- A calendar I expect isn't in the picker: it needs to already be added as an account in macOS (System Settings > Internet Accounts, or your organization's provisioning profile), and it needs to actually contain events for the window you're syncing.
- Two calendars have the same name: the command-line fallback script can't always tell calendars with identical display names apart. Rename one in Apple Calendar, or use the Mac app's picker instead, which lists both the calendar name and its account.
Contact
Please include:
- macOS version
- LocalCalSync version (About screen)
- What you selected as source/destination
- The Activity Log output from a Preview run, if the issue is sync-related
Response time
We aim to respond within 2 business days.