I have a peculiar problem with my app, probably of my own making but I can't figure out how or why. The session token remains valid for hours on end even through the night, and as far as I can tell, there is no background activity going on.
I left the app idle last night for example and the same token that was in use last night still works this morning. If I test my service by removing the token altogether, it correctly says that a token is needed (because it is a secure collection).
Now I must add that I did implement the solution at: https://getsatisfaction.com/apperyio/... to keep the user signed in, but I have made my code in such a way that the automatic login should only happen if the user selects 'Remember Me' at initial login. In this case (of the problem I'm reporting now), the user has not selected this and as far as I can tell from debugging, no auto-logging-in is happening. Even if there was, there would be a new token, not the same old one. So why is the session token remaining active and valid?
The only possibilities I can think of are:
The solution at the link above (perhaps the ajax call for timeout check) actually keeps the session active, meaning that auto-login is actually redundant? Could this be the issue? I doubt it but it is worth checking.
Some other background activity in my app is keeping the session active. Again I doubt this because the app shows up as idle in the console.
The default duration for Apperyio sessions has been increased from 120 mins to something else?
Please assist as I'm now behind on launching my app and this issue threatens to delay things further. I'd be happy to share my app with Support if required.