[Bug]: Permission.locationAlways.request() doesn't work on IOS

[Ellynnn]

Please check the following before submitting a new issue.

• I have searched the existing issues.
• I have carefully read the documentation and verified I have added the required platform specific configuration.

Please select affected platform(s)

• Android
• iOS
• Windows

Steps to reproduce

Check if Permission.locationWhenInUse.isDenied, if yes then request with Permission.locationWhenInUse.request(). If Permission.locationWhenInUse.isGranted then request for locationAlways with Permission.locationAlways.request()

Expected results

Bring user to app location setting page to Allow Location always just like in Android

Actual results

Nothing happened. Directly returned me with a PermissionStatus.permanentlyDenied

Code sample

Code sample

if (await Permission.locationWhenInUse.isDenied) {
    await Permission.locationWhenInUse.request();
    if (await Permission.locationWhenInUse.isGranted) {
     await Permission.locationAlways.request();
      if (await Permission.locationAlways.isDenied) {
        return false;
      }
    }
  }

Screenshots or video

No response

Version

11.0.1

Flutter Doctor output

Doctor output

[TimHoogstrate]

Dear @Ellynnn,

I have tested this with the provided example app but it seems to work as expected. What I don't fully understand is why: Bring user to app location setting page should happen. I see a pop-up asking the "always" permission.

Kind regards,

[LeonP2ER]

I have the same problem as @Ellynnn here. Does not work for me on an iPhone with iOS 17.0.3.

[LeonP2ER]

Seems to be related to / duplicate of #1152.

[TimHoogstrate]

Dear @LeonP2ER,

Can you create a new issue with all the required information like flutter doctor -v and steps to reproduce. Please try the example app to see if it is happening there. It seems to works in the example app with iOS 17.1 with the steps to reproduce.

Kind regards,

[LeonP2ER]

@TimHoogstrate I created #1211 :)

[github-actions]

Without additional information, we are unfortunately not able to resolve this issue. Therefore, we reluctantly closed this issue for now. If you run into this issue later, feel free to file a new issue with a reference to this issue. Add a description of detailed steps to reproduce, expected and current behaviour, logs and the output of 'flutter doctor -v'. Thanks for your contribution.