Error 908 ACCESS_FINE_LOCATION appears continously at init

You are right, Anke.
Thank you.
The full carpooling app I’m developing already does so for the user type “car driver”.
Because, it is a must for the platform to know where is the car, to arrange shared trips on the go.
What I was trying to do now, was making it optional to grant the permit for the user type “passenger” (wich only requires to know their position in case they want to use it as the origin point for a new trip, without having to type their current address).
In fact, it is not that important for most of the people, who will do the same trip every day (back and forth to workplace).

It looks like (despite this code has to be executed each time the app starts), if the user rejects granting the permission the first time they are prompted when the app starts, then they will be asked again the second time the app starts.
If they reject again, from then on, the denied event triggers and they will never be asked again (or at least during the same day, as far as I tested).
If they would want to change their choice, they will need to go throuhg the settings of the app to select a different option there.

Yes, this is how Google wants it to be

After a user rejected a permission, the idea is to not bother him anymore. If he changes his mind he can do so in the settings of tha app.

This is why it is important to explain to the user why a permission is needed before asking for it

Taifun

2 Likes

1 Like

Wow!
Brings the user directly to where they can change the permission settings.

Yes, that is the method to use, as it is not reliably possible to access the permission settings directly on all devices.