Security

Greetings,

 

We're in the proces of implementing onboard in our organisation and had several complaints about the quick connect app store link not working.

 

The cases we've reviewed all show that as soon as the user clicks the link for the Quick connect app they get a built-in browser telling them:

ERR_UNKNOWN_URL_SCHEME

market://details?id=com.arubanetworks.quickconnect.android

 

The workaround is to force the handset to use the network regardless, fire up chrome and complete the onboard process there. This is unintuitive and is generating more service tickets instead of less.

 

I've read some online forums and to me it looks like a fix is available by using webview with an intent instead of the custom URL scheme market://. 

Link: https://stackoverflow.com/questions/35442592/android-custom-url-scheme-refuses-to-work-how-to-navigate-back-to-android-app 

 

Any chance Aruba Networks will implement this to make our lives easier? Even better, can I change something in our current installation to make it work?

You need to bypass the captive portal browser on all platforms (Android, iOS, Mac) as they do not support lauching external applications or profile downloads. Unfortunately there's nothing we can. This is an industry-wide problem that the device manufacturers seamingly refuse to address.

 

Use the whitelist here to bypass the captive portal browser and allow access to the Google Play store: https://github.com/aruba/clearpass-cloud-service-whitelists/blob/master/onboard/onboard_android.md

Tim,

 

Brilliant, I didn't think about whitelisting the connectivitychecks. Going to test it with our users.

 

Thanks a lot!

Tim,

 

The original issue is resolved using the captive portal checker bypass. The downside is that most of our users do not make extensive use of the browser and or don't realise the lack of connectivity is because they aren't onboarded yet.

 

We will instruct them to use their browser to log on in the meantime but I can't help but wonder if the other format provided by Google would solve our issue. Google even suggest to use http over a straight market URL.. My bad, they suggest the opposite, but it's worth a try?

 

"In general, you should use http:// format for links on web pages and market:// for links in Android apps."

 

Link: https://developer.android.com/distribute/marketing-tools/linking-to-google-play.html#android-app 

 

Intent intent = new Intent(Intent.ACTION_VIEW);
intent.setData(Uri.parse("http://details?id=com.arubanetworks.quickconnect.android"));
startActivity(intent);

 

 

 

No. Bypassing the captive portal browser on iOS, macOS and Android is the only option.

Sounds like you've done your research. Could you shed a bit of light on the reasons why using http:// is not an option for Android?

It has nothing to do with the protocol. Captive portal browsers do not allow external launching or profile downloads. Both of which are required for onboarding.

This error is appeared because the WebView can't recognize the URL Scheme,for example, the WebView will usually recognize only http and https, anything other than these. So WebView cannot parse it to right place, we should use intent to redirect the url. for example – intent://,market://,app://,mail:// etc will not be recognized by webview unless we add a handler to handle these url scheme or by disabling these schemes and only load http and https schemes.

This error has no any specific solution till now. Android user and PC user all are facing this error which needs to be sought out. There's a long-standing bug in Chromium regarding how links without protocols are handled. It occasionally is patched, but seems to keep resurfacing. In some cases, prefixing your links with http:// (or https://) should resolve the issue for you.

Also, in some cases, try to add target="_blank" in your URL Scheme/Code. for example:

<a href="mailto:my@email.com" target="_blank">Link Text</a>


------------------------------
carlos ridg
------------------------------

Original Message:
Sent: Sep 01, 2017 10:30 AM
From: Arian Wubben
Subject: Android URL scheme error when opening play store link

Greetings,

 

We're in the proces of implementing onboard in our organisation and had several complaints about the quick connect app store link not working.

 

The cases we've reviewed all show that as soon as the user clicks the link for the Quick connect app they get a built-in browser telling them:

ERR_UNKNOWN_URL_SCHEME

market://details?id=com.arubanetworks.quickconnect.android

 

The workaround is to force the handset to use the network regardless, fire up chrome and complete the onboard process there. This is unintuitive and is generating more service tickets instead of less.

 

I've read some online forums and to me it looks like a fix is available by using webview with an intent instead of the custom URL scheme market://. 

Link: https://stackoverflow.com/questions/35442592/android-custom-url-scheme-refuses-to-work-how-to-navigate-back-to-android-app 

 

Any chance Aruba Networks will implement this to make our lives easier? Even better, can I change something in our current installation to make it work?