Device error messages

Below is a list of messages that a user may see on their device and what that message means:

Requesting session to be continued

Client: ADR Voalte One, ADR Voalte Me

Description: A user is logged in and the application is requesting the server continue that session

Mitigation: If stuck here and WiFi signal is good then the application is in a locked state. If force quit does not fix this problem you may need to remove and reinstall the application so the session is removed from the app.

Introduced Version: < 3.4

Too many ongoing calls

Client: ADR Voalte One

Description: The application can only have 2 active calls at a time. If the user attempts to start a 3rd call they will see this message.

Mitigation: The user needs to end one of their calls to make a new call.

Introduced Version: < 3.4

Waiting for server connection

Client: ADR Voalte One, ADR Voalte Me

Description: The app is attempting to establish communication with the server after having connected to the Voalte Service.

Mitigation: Check the WiFi bars to see if the device is getting a good signal.  If the signal is good (3 or more bars) and other devices are connecting then long click (4 sec) on the Voalte logo to display the configuration settings and confirm the Host domain is correct.  If so then get a log and file a ticket.

Introduced Version: < 3.4

Waiting for service proxy

Client: ADR Voalte One, ADR Voalte Me

Description: The app is waiting for the "service proxy" component to initialize, to then connect to the background service, which maintains the connection to the server.

Mitigation: If stuck here, something has gone terribly wrong. Force quit the app or reboot the phone. Grab logs and file a ticket if you can.

Introduced Version: < 3.4

Waiting for Voalte Service

Client: ADR Voalte One, ADR Voalte Me

Description: The application is waiting to connect to the background service which communicates with the server.

Mitigation: A force quit should fix this problem because it will restart both the app and the voalte service.  If Force Quit does not resolve the problem get a log and file a ticket.

Introduced Version: < 3.4

Reconnecting

Client: Messenger

Description: The application has lost its persistent connection to the server and is attempting to re-establish that connection.

Mitigation: If this status persists for an extended period of time, ask an SE to verify the nginx and IRIS services are up and running on the VDS without issue.

Introduced Version: < 3.4

Server busy

Client: Messenger

Description: The server is overloaded with requests and is not processing any new ones at this time.

Mitigation: If this status persists for an extended period of time, ask an SE to verify the nginx and IRIS services are up and running on the VDS without issue.  Refreshing the web page could cause further stress on IRIS, so be wary that trying this option will stop the issue.

Introduced Version: < 3.4

Failed to load the resource at

Client: Messenger

Description: Shown when the resource (conversation or profile) represented by the current URL could not be loaded from the server.

Mitigation: Typically this means that the resource has been destroyed or was only temporarily created before a page refresh and lost because it was not persisted with IRIS.  A common example of this status is opening a new conversation and not sending a chat message, but then refreshing the page; new conversations are not created with IRIS until their first chat is recorded.

Introduced Version: < 3.4