After a successful login attempt, The Appian Mobile App renders in “browser” mode instead of “native app” mode.
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.
This article applies to the Appian mobile app, versions 16.1 and later.
Last Reviewed: June 2018
© 2019 Appian. All rights reserved.