You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I downloaded the FlutterGeofencing code and tried to utilize the geofencing plugin in my project.
I created a button for registering geofences. After creating the google map, I pressed the button and got the following error on the Android emulator.
Since the error code means that the client doesn't have sufficient location permission to perform geofencing operations. I used the permission_handler plugin to assure that location permission is granted before initializing GeofencingManager. Permission is also granted before registering geofences.
However, I can successfully add the geofences without any issues when using the physical Android device. Is it possible that there's a conflict between google map and geofencing in the emulator but not in the physical devices?
Below is my flutter version. Any feedbacks are appreciated. Thank you for your time.
The text was updated successfully, but these errors were encountered:
I downloaded the FlutterGeofencing code and tried to utilize the geofencing plugin in my project.
I created a button for registering geofences. After creating the google map, I pressed the button and got the following error on the Android emulator.
Since the error code means that the client doesn't have sufficient location permission to perform geofencing operations. I used the permission_handler plugin to assure that location permission is granted before initializing GeofencingManager. Permission is also granted before registering geofences.
However, I can successfully add the geofences without any issues when using the physical Android device. Is it possible that there's a conflict between google map and geofencing in the emulator but not in the physical devices?
Below is my flutter version. Any feedbacks are appreciated. Thank you for your time.
The text was updated successfully, but these errors were encountered: