@DTS Engineer - could you update the link to the story - the original has been removed. Or...summarize here why we can no longer do this. I am trying to do this too. Users are dumb...and on iOS, if Global GPS is disabled, then routing to the app permissions page is useless because app Location setting is greyed out. Global device GPS needs to be enabled first in order for the user to change the app level location setting. So...to hold the users hands...which is OFTEN....we first need to bring them to the Settings -> Privacy & Security -> Location settings to enable GPS at the device level first. After they have done that, then we need to route the user to the App Location setting to change it (if necessary). I can guarantee you that if app level location is greyed out that MOST users aren't going to know that they must first enable device level GPS. Relying on the user to just know this is a BAD UI design. This also impacts the apps ability to streamline the user experience...get them right to where they need to be so they can get back to our app. Like always, this is all clean and simply on Android, but for whatever reason it's a clunky mess on iOS. What justifiable reason does Apple think routing a user directly to the setting in question is somehow a harmful user experience?

I have users that have updated their iPhones to 18.3.1 and it is breaking my app. I need to download 18.3.1 emulator to see what's going on but there appears that 18.3.1 is not available for simulator download yet. This crap happens all the time with Apple. NEVER with Android.