On Android, when the user denies access to precise location but grants access to coarse location, they are asked again if they want to grant precise location. If denied, Error(cause=PermissionDenied(forever=true)) is returned.
On iOS, when the user denies access to precise location, the library returns an inaccurate location.
The behaviour of these 2 platforms should be the same.
I propose to create an option emitCoarseLocation when the user denies access to precise location, and emitCoarseLocation is true, it should emit location, if emitCoarseLocation is false, it should ask again for precise location, if denied, an error should be returned PreciseLocationDenied.
On Android, when the user denies access to precise location but grants access to coarse location, they are asked again if they want to grant precise location. If denied,
Error(cause=PermissionDenied(forever=true))is returned.On iOS, when the user denies access to precise location, the library returns an inaccurate location.
The behaviour of these 2 platforms should be the same.
I propose to create an option
emitCoarseLocationwhen the user denies access to precise location, andemitCoarseLocationis true, it should emit location, ifemitCoarseLocationis false, it should ask again for precise location, if denied, an error should be returnedPreciseLocationDenied.