Mobile - notification shows "expired' even when user is not logged out
Per Elias, "There are two things happening here...
Session Expired: Please log in to continue receiving notifications. Sessions for DoD Platform One are configured to expire every 1 day When you login the app is scheduling a local notification to trigger when the session expires. The expiration timestamp is set based on the more recent session created. Because of the session length for SSO differs from the mobile session length, when you login with SSO the more recent session will have the expiration timestamp based on the SSO session length instead of the mobile length. This is happening cause of the way the server recognizes the session to be from mobile if the deviceId is attached. In the case of SSO login is the deviceId is attached after the session was created. This means that we are going to have to add a handler for SSO login to recognize that it was from mobile without a deviceId. Invalid or expired session, please login again is an error thrown by the server when the session is no longer valid, this is happening cause when the app tries to fetch the message from the server when it receives a notification, the session token being used is not valid at the time. My thinking is that this is somewhat related to #1. Additionally I can say that it was an oversight in implementation to prevent or cancel fetching the notification with tokens of expired sessions. I can also say that this small window of active sessions may have been a use case that we forgot to take into account when the feature was built.
Clearly you have managed to find this issues and we can now go and fix them
FYI: @Scott Bishel / you may want to take a look at the server side to help fix the session length when SSO login is initiated from the mobile app."