I have indications that ACCESS_BACKGROUND_LOCATION may be Denied(shouldShowRationale=false) while ACCESS_FINE_LOCATION is Denied(shouldShowRationale=true). It then seems like ACCESS_BACKGROUND_LOCATION shifts to Denied(shouldShowRationale=true) once ACCESS_FINE_LOCATION is granted.
I have not yet confirmed this but something seems to be acting strange with these two. If the above description is correct, the proposed solution in this PR is insufficient (though covering an unexpected gap that exists today).
I think someone should take a closer look and disprove the above theory before merging this (that'll probably be a few months out on my end - if even then).
Adding the fix I proposed in #1781
Fixes #1781
Additional complication:
I have indications that
ACCESS_BACKGROUND_LOCATION
may beDenied(shouldShowRationale=false)
whileACCESS_FINE_LOCATION
isDenied(shouldShowRationale=true)
. It then seems likeACCESS_BACKGROUND_LOCATION
shifts toDenied(shouldShowRationale=true)
onceACCESS_FINE_LOCATION
is granted.I have not yet confirmed this but something seems to be acting strange with these two. If the above description is correct, the proposed solution in this PR is insufficient (though covering an unexpected gap that exists today).
I think someone should take a closer look and disprove the above theory before merging this (that'll probably be a few months out on my end - if even then).