carp-dk / carp-dk/carp.sensing-flutter
Location probes never ask for location permission
- Dominant language
- Dart
- Stars
- 84
- Forks
- 31
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 6
Description
The location, geofence and mobility sampling schemes are declared with a plain DataTypeMetaData, which cannot carry permissions, so the probe asks for none and the location plugin ends up asking Android natively instead. That native request is outside CAMS' control, so it collides with any other permission dialog being shown at the time.
Contributor guide
No contributing guide indexed for this repository
Research direction
Trace where the location, geofence, and mobility sampling schemes are declared and how DataTypeMetaData is used for their permissions. Then inspect the location plugin's permission flow; the work is done when CAMS requests the required permissions itself and no longer triggers an uncontrolled native dialog that can collide with another permission request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, dart, flutter
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100