I have done a lot more research and testing, and this is what I have found.
First, lots of people are having the same issue, as you can see in the Google Play store app reviews:
https://play.google.com/store/apps/details?id=com.arubanetworks.quickconnect.android&hl=en
“Buggy and untested. Doesn't register the mime type correctly. Due to this I had to download a different browser and then open the .networkconfig file on this app, that's when it worked. Just test your apps on multiple Android devices before marking your tickets as not an issue.”
“Does not work since the newest software update Ever since my most recent software update, the app stopped working for me. I got kicked out of my WiFi at work and I am always getting the message "unable to configure device." My work hasn't changed anything on our end and seeing the other reviews makes me believe it's the app. I've even tried changing the password on my phone and it still doesn't work. PLEASE FIX THIS!”
“Device will not configure When I got into work this morning I was unable to connect to our network. I tried to reprovision my device and all the quick connect did is reroute me to the Aruba clear pass website for our company. I've downloaded the configuration file countless times and the app still will not provision my device.”
So I would recommend that Aruba's development team actually look at user reviews to see what people’s real-world experience is. This is frustrating and embarrassing when putting it in front of a customer who is expecting results.
However, this got me testing some things. The first thing I tried was to uninstall Google Chrome on my Android device. This is not possible, but I was able to uninstall the latest updates, and set the default browser to the builtin “Internet Browser”.
I used the default browser and was able to properly register, install QuickConnect, and then install the network configuration.
Next, I repeated the process using Firefox as the browser. Firefox failed at the registration phase, saying that the browser is unsupported, and to use Google Chrome (!)
Next, I tested the process with the out-of-date Google Chrome, and was again able to provision completely.
Next, I updated Google Chrome to the latest version, and as I suspected it was no longer able to launch quickconnect, with the same error: “All apps associated with this action have been disabled, blocked or not allowed".
So it appears that the problem is with QuickConnect not registering the mime type properly with the latest version of Chrome on Android.
Since it is unlikely that we will be able to force thousands of users to downgrade their browser, I think the ball is in Aruba’s court, to fix and test QuickConnect on the latest Android Chrome Browser.