We list known issues here along with workarounds while fixes are prepared for the next App Store build.
Changing the in-app language can cause GeoNap to close unexpectedly
- Issue Reported
- 11-Sep-2026
- Issue Description
- In some cases, changing GeoNap's language in Settings can cause the app to close unexpectedly instead of applying the new language right away.
- Work Around
- Simply reopen GeoNap — your newly selected language will already be applied, and nothing else is affected.
- Expected Resolution
- N/A
- Issue Resolved
- Build 1.180.20260911
GeoNap may close unexpectedly during an automatic calendar scan
- Issue Reported
- 11-Sep-2026
- Issue Description
- If Calendar Scanning is turned on with Scan Mode set to Automatic, GeoNap can occasionally close unexpectedly in the background while a scheduled scan runs. This only happens while GeoNap is not the active app on screen.
- Work Around
- Reopen GeoNap. Your alarms, settings, and any previously found calendar scan results are unaffected.
- Expected Resolution
- N/A
- Issue Resolved
- Build 1.180.20260911
Duplicate Live Activity cards may appear on Lock Screen for the same alarm
- Issue Reported
- 24-Aug-2026
- Issue Description
- For Platinum-tier users with Live Activity / Dynamic Island enabled, an active alarm can occasionally show two Live Activity cards on the Lock Screen instead of one, each with a slightly different distance-remaining value. This can happen if the app is closed and then reopened in the background (for example, by an incoming location update) while an alarm is already being tracked.
- Work Around
- This is cosmetic — your alarm still fires correctly either way. You can swipe away the extra card, or just ignore it; it will clear on its own once the alarm fires or is turned off. You can also clear it directly from GeoNap: go to Settings → Support → Clear Stale Notifications, which removes any leftover Live Activity or notification that no longer matches an alarm in your list.
- Expected Resolution
- N/A
- Issue Resolved
- Build 1.170.20260821
Arrival alarm audio plays through phone speaker instead of connected Bluetooth headphones
- Issue Reported
- 22-Aug-2026
- Issue Description
- When an arrival alarm (Location or Transit) fires while your iPhone is connected to Bluetooth headphones or earbuds, the alarm notification appears correctly, but the alarm sound plays out loud from your iPhone's built-in speaker rather than through your headphones.
- Work Around
- There isn't a workaround, because this isn't a GeoNap issue — it's how iOS handles alarms system-wide. Apple's built-in Clock app behaves the same way: alarms always play through the iPhone's speaker, even with Bluetooth headphones connected, so you're guaranteed to hear the alert even if your headphones are out of your ears, powered off, or out of range. GeoNap's alarms are built on Apple's own AlarmKit framework specifically so they behave exactly like a native Clock alarm, including this safety behavior.
- Expected Resolution
- N/A
- Issue Resolved
- Build 1.170.20260821
