KB-1594 Appian mobile app renders in "browser" mode instead of "native app" mode

Nick Vigilante — Mon, 11 Jun 2018 19:47:09 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 6/11/2018 7:47:09 PM

Symptoms

After a successful login attempt, The Appian Mobile App renders in “browser” mode instead of “native app” mode.

Cause

If upon opening Appian, the user is first directed to a custom login authentication site (through SSO or some other custom authentication configuration), when the User is redirected back to the Appian server after authentication, the Appian server does not receive the correct HTTP response code (302) and/or the original URL that was initially requested by the Mobile App.

Action

After users are logged in on the site handling authentication, the site must respond back to the Appian server’s HTTP GET/POST request with a 302 or 301 HTTP response code. The URL the user is redirected back to must also contain ‘/suite/tempo’ or ‘/suite/sites’. This can be implemented on a server level or through javascript.

Affected Versions

This article applies to the Appian mobile app, versions 16.1 and later.

Last Reviewed: June 2018

Tags: Mobile

KB-1305 Appian mobile app renders in "browser" mode instead of "native app" mode

Nick Vigilante — Tue, 07 Mar 2017 20:55:18 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 8:55:18 PM

Symptoms

After a successful login attempt, The Appian Mobile App renders in “browser” mode instead of “native app” mode.