[Help Wanted]: Polygon geofencing without FOREGROUND_SERVICE / FOREGROUND_SERVICE_LOCATION
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
Research direction
Start by reading the Android geofencing and foreground service documentation and the plugin's PolygonGeofencingService entry point. Reproduce the merged manifest warning after removing the foreground service permissions, then trace how polygon geofencing is promoted. Done means the issue's recommended Android approach is documented or implemented and polygon geofencing works without those permissions.
Written by the indexing model from the issue text.
Description
Required Reading
- Confirmed
Plugin Version
5.9.0
Mobile operating-system(s)
- iOS
- Android
Device Manufacturer(s) and Model(s)
Any Android
Device operating-systems(s)
Any Android
What do you require assistance about?
Hi @christocracy ,
We utilise your plugin for our geofence based checkins - both circle and polygon. Up until now, this has been working great. With Google's updated policy around not permitting FOREGROUND_SERVICE / FOREGROUND_SERVICE_LOCATION for geofencing coming into force soon, we are looking at what we need to change in our implementation to comply with this policy update.
The nature of our app is that it needs to run in the background a lot of the time and check people in and out of work places. One of the things that has come up in testing is that if we remove those permissions from our merged manifest, we see warnings such as the following:
10-22 17:09:33.751 WARN [AbstractService a] ⚠️ Cannot promote PolygonGeofencingService: FGS permissions not declared in the merged manifest (running unpromoted)
Is there a recommended way to use polygon geofencing on android going forward?
Thanks
Chris
[Optional] Plugin Code and/or Config
[Optional] Relevant log output
- Dominant language
- Dart
- Stars
- 732
- Forks
- 287
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from transistorsoft/flutter_background_geolocation
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
transistorsoft/flutter_background_geolocation#1724 · 2 comments ·
-
[Bug]: tslocationmanager still depends on bcprov-jdk15to18 1.84 (CVE-2026-8763, CVE-2026-13506)Openbug
Difficulty 3/5 1-2 days Newbie friendliness 54/100
transistorsoft/flutter_background_geolocation#1725 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
transistorsoft/flutter_background_geolocation#1719 · 8 comments ·
All issues in transistorsoft/flutter_background_geolocation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
google/skills_lint.dart#165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
good first issue help wanted translation
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
blankframe-tech/ThrottleIQ#23 ·
Maintainers usually reply within 5 days
-
good first issue mobile P0 size:S
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
trufi-association/trufi-core#1024 ·
Maintainers usually reply within 14 days