roop
commented
2 years ago A couple of assumptions:
- When you got "session is expiring", I think you might have seen an alert but you didn't click anything in it then. Is that correct?
- After 13 hours, you said you clicked "Renew Session". I presume it was in the alert from (1). Is that correct?
If the above assumptions are correct, I suspect this is what might have happened:
- When session is about to expire in 30 mins, the app is in the foreground, so the notification is converted into an alert in the app. The alert would say "Your VPN session is expiring".
- You did not click anything in that alert at that time, so the alert remains
- You allowed the device to suspend
- You wake up the device after some time
- On wakeup, the app tries to show an alert ("You VPN session has expired"), but since an alert is already being shown ("Your VPN session is expiring"), the app schedules it to be shown after the current alert is dismissed
- You click on "Renew Session" in the "Your VPN session is expiring" alert. The app starts the connection flow, dismisses the alert.
- The app shows the "You VPN session has expired" alert. The connection flow continues and proceeds to connect successfully.
- You click on "Ignore" in the "You VPN session has expired" alert and you find that the app is already connected.
yesterday evening I got session expired and now roughly 13 hours later I click "renew session" , click on "approve" but client (current Appstore version) doesn't respond to the received OAuth token.
The problem is the "session has expired" notification seems not to be integrated in the App anymore. As if, because 13 hours were passed, the App isn't fully aware of the notification state and the notification doesn't disappear however the App received the OAuth token succesfully.
When I click "ignore" the client is connected successfully.