Repository navigation
Troubleshooting
| Problem | Check |
|---|---|
| Menu bar indicator is missing | Reopen Alertivity. In Menu bar settings, enable Show indicator and disable Only show on high activity. A hidden Dock icon does not mean the app has quit. |
| No notifications | Follow the notification setup paths, check Focus and the selected Cooldown, then check when alerts are sent. |
| Custom settings are locked or Pro is unavailable | See Pro purchase checks. |
| Detection or processes are missing | See checks below. |
| Readings differ from Activity Monitor | Compare intervals and units using reading limitations. |
| Activity Monitor opens without finding a process | See permission checks below. |
| Launch at login fails | Follow the General settings paths. If registration fails, Alertivity refreshes its toggle to the system state. |
| Welcome guide or settings differ | Compare the installed build with the version note on Home. Reopen onboarding using the first-launch instructions. |
In the Mac App Store build, custom thresholds, cooldown, and duration require a verified Pro purchase. Hover over the lock beside a control for its explanation. Free monitoring continues with default values; your saved custom settings are preserved. The source build has no Pro tab or purchase requirement.
- Purchase options did not load: check your connection and choose Load Purchase Options in Settings → Pro. If Pro is unavailable, restoration is still available for existing purchases.
- An existing purchase is locked: use the App Store account that bought Pro, then choose Restore Purchases. The app also checks access when it becomes active again.
- No purchase was found: confirm the App Store account and build variant. A source build does not create an App Store purchase.
- Purchase awaiting approval: wait for approval; customization unlocks after the verified transaction arrives. Cancelling a purchase grants no access.
- Purchase or restore failed: read the note below the buttons and retry. Unverified transactions do not unlock Pro. A refund or revocation restores Free defaults without deleting customization.
See Free and Pro settings for the feature boundary. Developers testing local products should check the StoreKit configuration.
Check the build variant, check Detection settings, and wait for activity to remain above the limits for the selected duration. Check whether disk is the selected trigger, which hides the process section. Inspect logs if process sampling fails. Accessibility approval does not unlock process sampling in the sandboxed target.
Open Apple menu → System Settings → Privacy & Security → Accessibility, and separately Privacy & Security → Automation, to check access for Alertivity and System Events. Grant any requested permission, then retry. Section names can vary by macOS version. Search manually in Activity Monitor if UI automation fails or the sampled process has exited.
Use the repository issue tracker. Include the app version/build variant, macOS version, steps to reproduce, what you expected, what happened, and relevant settings. Include the commit ID if you built from source.
In Console.app, filter by subsystem com.Nobby.Alertivity (sandboxed) or com.Nobby.Alertivity.standalone (source build), with categories lifecycle, metrics, notifications, purchases, or reviews. Review logs and screenshots before sharing; remove private process paths and unrelated personal information.