Secure Client 5 for iOS URI handler problems

[aswit]

Hello,

We have been using Clientless SSL VPN access on Apple iOS devices from our internal portal for many years without any problems. The connection is made VIA a URI (eg. anyconnect:[//]connect[/]?[name=Description|host=ServerAddress] [&Parameter1=Value&Parameter2=Value ..]) that opens the Cisco Secure Client app and automatically connects to the VPN. However since the 5.1 release we have noticed some problems:

• Even if the VPN connects it redirects the user to the onerror URL. You can see the VPN symbol appear after a few seconds but this is confusing users into thinking the connection failed.
• When you specify anyconnect:close for either the onsuccess or onerror the VPN client closes before it has a chance to connect.

Is this a known issue with the application on iOS?

We are using the latest version of everything. Secure Client v5.1.16.264 and iOS 26.5.

Thanks

[olasupoo]

Hi Aswit,

Looks like the URI handler is acting on the result too early in 5.1. The tunnel does come up (that's the VPN icon you see a few seconds later), but onerror/close runs before the connect finishes, so close kills the app and onerror makes a working connection look like it failed.

There's an old onerror/onsuccess bug, CSCui07396, but that one's logged against the Android client so it isn't really yours. I haven't seen this exact iOS behaviour written up anywhere, and there are a couple of other 5.1 iOS app issues people have raised here, so I'd open a TAC case with your versions (5.1.16.264, iOS 26.5) and the two repro steps.

For now, take anyconnect:close out of onsuccess/onerror, since that's what's closing it mid-connect. If you can get hold of an older 5.1 build, try it and see which version broke it, that'll help the case. iOS 26.5 is also very new so worth flagging both to Cisco.