iOS 26 fails to automatically switch to [system settings - personal hotspot ] directly from application ]

my application supports automatically switching to [Personal Hotspot] directly

What API was it using to do that?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

App-Prefs:INTERNET_TETHERING

OK, that’s what I suspected. Have a read of Supported URL Schemes.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Sorry I didn’t respond earlier. You replied as a comment and I missed that )-: It’s better to reply as a reply. See Quinn’s Top Ten DevForums Tips for this and other titbits.

Does this suggest that iOS 26 does not support this functionality?

Yes.

Moreover, is it possible that versions of iOS 18 and earlier may also not support this behavior in the future?

I don’t normally comment on The Future™, but in this case the future is today. This technique is already unsupported on iOS 18. It just happens to work, but that’s an implementation detail.

As to what you should do, I agree with Scott’s advice on your other thread.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thank you for your kind and thoughtful response. I would like to confirm once again. So can I assume that iOS 26 only provides an API to jump to the [Settings app] path? Will attempts to jump to other submenus in the system settings be redirected here by default?

iOS 26 only provides an API to jump to the [Settings app] path?

Not quite. It has APIs to get to various locations within Settings. I’ve includes links to all the ones I know about in Supported URL Schemes.

Will attempts to jump to other submenus in the system settings be redirected here by default?

If you attempt to navigate to specific Settings pages by opening undocumented URLs, you’re exercising implementation details. The exact behaviour you get isn’t documented and may change from release to release.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

If you attempt to navigate to specific Settings pages by opening undocumented URLs, you’re exercising implementation details. The exact behaviour you get isn’t documented and may change from release to release.

We found that not only did the redirection to the [Settings app - Personal Hotspot] not work, but redirection to the [Settings app] itself is also ineffective.

Does iOS 26 completely prohibit the use of private APIs? And is the only recommended method for opening the [Settings app] now the use of [UIApplicationOpenSettingsURLString] API?

Does iOS 26 completely prohibit the use of private APIs?

It’s best not to think about this stuff in terms of public and private APIs. Rather, there are APIs, the public things that we specifically publish for third-party developers to use, and implementation details, meaning everything else. Once you think about it this way, the consequences are clear:

• If you use APIs, you can reasonably expect consistent behaviour.
• If you rely on implementation details, the behaviour can change between different OS releases, different device types, different users, and so on.

And is the only recommended method for opening the [Settings app] now the use of [UIApplicationOpenSettingsURLString] API?

Supported URL Schemes lists lots of different APIs for opening Settings, each focused on a specific test. But if you want to open your app’s main settings then, yes, UIApplicationOpenSettingsURLString is the API for you.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"