Tango Reserve Mobile Application Troubleshooting

Modified on Tue, 3 Mar at 1:20 AM

This article is to provide instructions for basic and advanced troubleshooting to resolve issues with the Tango Reserve mobile application. 

 

Basic Troubleshooting

 

Step 1 – Check App Store for application updates

Step 2 – Make sure mobile device is up to date with its current software

Step 3 – Close out all applications

 

If the above does not resolve the issues, attempt the following steps:

 

Step 1 – Uninstall the application

Step 2 – Restart the mobile device (this will assist with clearing the cache as it relates to the application)

Step 3 – Reinstall the application

Step 4 – Set up the application (if you have SAML, refer to the following link to set up your SAML application /support/solutions/articles/159000428138 )

***NOTE:  If you’re using MDM (Mobile Device Manager), be sure to refer to this article as it may resolve issues dealing with the MDM configurations. /support/solutions/articles/159000427321 ***

Step 5 – Attempt to login

 

iOS SAML Login Troubleshooting

 

At times clients may have an internal token session longer than the 365 days that Tango Reserve’s SAML token session allows.  In the event this happens, it may cause issues with iOS users accessing the application using SAML as their internal SAML session token expiration date appears to be valid.  If iOS users have issues logging into the application, please attempt the following steps:

 

Step 1 – Close out all applications

Step 2 – In the Safari browser, attempt to access this URL:  https://login.microsoftonline.com/common/wsfederation?wa=wsignout1.0

***NOTE:  You should get a logout page.  Once you get confirmation, proceed to Step 3***

Step 3 – Clear all cookies and cache

Step 4 – Restart device and reattempt the log in

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article