Supported Mobile Clients and EMM Suites Requirements
Browser connectivity to Qlik Sense requires that the Browser, VPN, and all Network Infrastructure between the Mobile Device and Qlik Sense Enteprise supports HTML5 Websockets. Some components may require tuning to ensure that the long-duration websockets Qlik uses are not inappropriately terminated due to inactivity.
On iOS the browser must use Apple's newer WKWebView rendering engine. Older browsers that still use the now-deprecated UIWebView rendering engine do not support the HTML Stylesheets that Qlik Sense uses, and may not display all content correctly. UIWebView may also fail to route websocket traffic correctly through Per App VPN to on-premise instances of Qlik Sense Enterprise.
In rare cases it may be necessary to configure Qlik Sense to keep idle websockets alive, otherwise network infrastructure may terminate those connections to the Associative Engine during user inactivity. Refer https://support.qlik.com/articles/000055708
Qlik Sense Mobile additionally requires that the VPN Client supports Split Tunneling so that localhost TCP traffic within the app is not inappropriately routed to the VPN Server. This functionality is broken in iOS 13.0-13.3, so 13.4+ is strongly recommended.
The MobileIron Sentry VPN Server requires minor tuning (TcpIdleTmoMs) to prevent aggressive termination of the websocket connections. The Web@Work browser must be configured to use use_WKWebView=true. The MobileIron Tunnel (app-proxy) requires a Custom Data key DirectLocalhost=true to enable Split Tunneling and prevent mis-routing of app-internal TCP traffic.
The PulseSecure VPN may be used together with several EMM products. Anecdotal field (GSK) feedback is that it works with browsers, but has not been validated by Qlik
Citrix Secure Web uses the Apple-deprecated UIWebView webkit and does not route websocket traffic correctly. Public sites will appear to work but routing traffic through the Netscaler to a private instance of Qlik Sense will fail. Consider using Safari with the Citrix VPN instead.
Unsupported EMM Suites
Product Management can be motivated by market demand and tangible commercial pressure to research and validate additional VPN technologies and EMM Suites.
The choice of Enterprise Mobility Management (EMM) Suite is largely irrelevant to success. Most support the AppConfig standard that can be used to configure applications on the Mobile Device.
What is important is the VPN technology that is managed by the EMM and may be included with it, which must support the Requirements listed above.
Many Enterprise Mobility Management suites include an App Wrapping capability. This can be used to programmaticly attach EMM functionality such as a VPN Client or Multifactor Authentication mechanism to an existing iOS app. Customers/Partners may propose that Qlik supply them with the Unsigned IPA of Qlik Sense Mobile so that they can attempt to use this capability to create a customized version of Qlik Sense Mobile that might work in their environment. The IPA can be supplied upon request to the Product Manager (via your Account Manager), BUT with the following conditions:
App Wrapping is unproven with Qlik Sense Mobile.Qlik has no record of any attempt at AppWrapping being successful with Qlik Sense Mobile. The IPA contains a mixture of XCode and compiled C++, uses TCP to address components within the app, and relies on Split Tunneling for proper routing. It has proven too complex for automated augmentation using AppWrapping or even the features of the 3rd-party serviceAppDome.
The App Wrapping procedure and any iOS app that it produces is entirely unsupported by Qlik.