Open Safari after Captive Network Assistant authentication

To add - it appears that opening Safari from a full URL was possible in iOS 10.0.x but at some point Apple changed it.

As there's very little documentation it's somewhat frustrating that things like this change and there's no suggested workarounds or even reason for the change.

But clearly a Web experience in the CNA MicroBrowser is nowhere near as good as in Safari [or Chrome, or whatever].

We've run more tests and are able to open any App that supports the URL Scheme from within the CNA Tear Sheet. Just not Safari, which does not support Apple's own URL Scheme.

The mind boggles. Any input here, folks?

Hi @AlasdairScott,

You got any work-around here?

I have a router that opens the Apple CNA on a captive portal with a button to accept the terms & conditions.

When the users accept the terms, the router unlocks the connection and redirect the user to a welcome page with a link.

On iOS 10.2.1 when I click on the link (it is an absolute link "https://mydomain.it/mypage") the CNA is automatically close and Safari is opened with the link.

On iOS 10.3.1 the link is opened inside the CNA with all limitations of the case (limited js support, no localstorage, ecc...)

How do I fix it?

I filled a bug report now.

I filled a bug report now.

What was the bug number?

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi, I am having the same issue in a captive portal with a landing page, and it is also critical for me. ¿Do you have any feedback from Apple?

It is still working for earlier versions, but stopped working from 10.3.

Thanks

This http://i.imgur.com/mN3qDlV.png

Thanks! 🙂

Thanks.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

ps For the sake of Future Quinn™, who likes to copy’n’paste bug numbers, that is 31785574, which got dup’d to 31534659.

hi,

how can I follow the status and fate of bug report 31534659?

cheers

how can I follow the status and fate of bug report 31534659?

If you file your own bug about this, it will get closed as a dup of 31534659 at which point you’ll be able to see basic status information about that bug (namely, it’s open/close state). Beyond that, there’s no official mechanism for getting more details about other people’s bugs.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi,

nothing

We are facing the same problem and tried different solutions. Any progress on this?

Thanks

Roland

The issue status is still open.

Same issue in 10.3.2

the problem is critical

@eskimoYou can ask some iOS developers to fix this issue in the next version of iOS?

We're also having this problem. Really hoping Apple will respond with it's plans RE this bug.

@eskimo please guys ... fix this! It is very annoying.

It appears that iOS 11.0 [15A278f] pre-release build now reverts back to how 10.2.x used to work and once authenticated, a direct link will open in Safari.

YAY, THANK YOU APPLE!

Hopefully this remains the case for the GM release of iOS 11 :-)

I just wanted to provide some general guidance here.

AFAICT all of the problems described here are related to built-in components of the system, that is, the captive network sheet and Safari. This makes them somewhat outside of the scope of DevForums, where the focus is on APIs [1]. It’s fine to discuss user-level stuff here, but you’re unlikely to find folks who are experts in that field.

As AlasdairScott pointed out, there have been some improvements in this space in recent releases. I encourage you to retest your setup with the latest pre-release system software, both minor releases (like the current iOS 10.3.3 beta 5) and major releases (like iOS 11 beta 2).

If the problem you’re seeing is not fixed in the latest major release, you should file a bug about it (unless you’ve already done so, in which case thanks!). I realise that there’s a number of bugs on file already about this issue, but your own bug report will ensure that your specific case is covered.

Please post the numbers of any bugs you file, just for the record

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

[1] There is a supported API for interacting with the captive network subsystem, namely NEHotSpotHelper, but AFAICT that’s not what we’re discussing here.

I tested the bahavior of CNA again in the iOS 11 GM released yesterday.

The direct link is opened in Safari, but the CNA does not close itself now.

The user will need to tap "Done" to proceed.

Do you meet the same problem?

Yes, I'm getting the same behavior. It's the same behavior of public beta8 and public beta9.

In my captive portal, when I conclude the login procedure if i click on a link inside the CNA, link is opened in Safari but underneath the CNA and is shown only when the user taps on "Done".

Is this behavior intended or not?

@eskimo I know that this forum is intended for discussions about APIs, I just wanted to make sure if this behavior is intended or not and if not, then submit a bug.

Thank you for your reply.

Everyone who met the problem please submit bug report to Apple via the "feedback" app in iOS 11 GM, thanks!

I know that this forum is intended for discussions about APIs, I just wanted to make sure if this behavior is intended or not and if not, then submit a bug.

Here’s the thing: it doesn’t matter if the behaviour is intended — if something is giving you grief then it’s always bugworthy.

Share and Enjoy
—
Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thanks Quinn - I've reported this via Apple Bug Reporter for iOS GM. [Bug # 34657459]

Most anoyingly it was fixed and 100% working on the beta releases, then for GM seems to introduce brand new behaviour that's unepxected and negatively affects the User Exprience.

It means users are far less likely to notice that once they have logged-in they've been directed to a specifically chosen page with full Safari functionality.

We will continue testing and trying various solutions but looking at this thread, none of the lovely folks here have found anything to solve it!

Upgraded to iOS 11.1 beta today. The CNA behavior is still the same as 11.0. 😢

I submitted feedback again.

Yes, this behaviour is really a nonsense and not possibile that this is "as intended".

Please fix guys. Where can I submit a bug or push/follow this # 34657459 ??

Many thanks