Location-based reminders are designed to trigger a notification precisely when you arrive at or leave a specific area (like your home, gym, or office). If these reminders are not firing correctly, it is usually due to strict system-level permissions or a known technical issue with the underlying location services.
⚠️ Known Issue: Google Geofencing SDK
Our development team has identified a recurring issue specifically for Android users involving the Google Geofencing SDK (part of Google Play Services).
The Problem:
There is a known bug in the Google SDK that causes "location signals" to hang or fail to report to third-party apps like Habitify. This means that even if your GPS is active and your permissions are correct, the system fails to tell Habitify that you have crossed the boundary.
The Status:
Because this is a system-level issue on Google's side, we are currently waiting for a stable update to the Google Play Services framework. We are monitoring their developer trackers closely and will update our integration as soon as a fix is deployed.
What you need to do:
At this stage, there are no specific settings to change. Once Google releases a fix, the functionality will be restored automatically via a system or app update.
Technical Limitations to Keep in Mind
Even when the system is working correctly, there are inherent behaviors in how mobile devices handle location that you should be aware of:
System Latency: Both iOS and Android may wait a few minutes after you enter a zone before notifying the app to prevent accidental triggers (e.g., just driving past a location).
The "Radius" Factor: If your geofence radius is too small (less than 100 meters), GPS "drift" might cause the reminder to trigger late. We recommend a radius of at least 150-200 meters for best results.
Signal Strength: If your location is in a basement or a thick concrete building, your phone may lose the signal before it can register your arrival.
Still not working?
If you have verified your basic location permissions are active and reminders still won't fire, please wait for the official update. We are continuing to monitor the status of the Google SDK fix and will ensure the app is ready as soon as the system-level bug is resolved.