Please provide the following:
- SDK Version: 39
- Platforms(Android/iOS/web/all): Android & IOS
I’ve implemented geofencing in my app following the documentation on https://docs.expo.io/versions/latest/sdk/location/#geofencing-methods.
I am facing several weird outcomes:
1.I defined 2 background tasks with TaskManager.defineTask (https://docs.expo.io/versions/latest/sdk/task-manager/) - TaskA and TaskB. Then I registered geofences with locationStartGeofencingAsync for Loc1 with TaskA and another for Loc2 with TaskB. (i.e. locationStartGeofencingAsync(TaskA,Loc1) and locationStartGeofencingAsync(TaskB,Loc2) ).
geofence trigger for Loc1 => TaskA,
geofence trigger for Loc2 => TaskB
geofence trigger for Loc1 => Task A & Task B
geofence trigger for Loc2 => Task A & Task B
I can work around it, BUT my question is: isn’t it possible to define different geofence task for different geofence?
- another unexpected outcome is that on IOS I receive exit notification even when notifyOnExit is set to false. Same for entry on IOS when notifyOnEnter is set to false. (works perfectly on Anrdoid).
I can work around it as well, BUT it is missing the point of notifyOnEnter and notifyOnExit.
Is this the expected behaviour on IOS?
@charliecruzan I believe you are the Expo expert for this topic. Appreciate your thoughts on the above. Thanks!