Here's some more feedback which I hope could be passed on to the developers:
The account on the device should never (!!!) expire. In other words, once an account is set up on the device, the device should remember this account and keep it flagged as active forever (!!!), no matter what happens on the device, including exiting from the AirDroid app and including reboots. The only time the account on the device should be expired or deleted is if the AirDroid app is uninstalled, or perhaps during some sort of new, explicit "disconnect" request that the user would have to manually invoke.
If the account expires on the server, I understand that we would need to re-login on the server. However, even in the case of server re-logins, the app, itself, should always (!!!) know what account was previously set up on it, and the app should always (!!!) use that same account during server<=>app reconnection attempts. So if the server session expires and is restarted, the app should be totally ready and fully configured to automatically reconnect to the server, without the user ever having to re-enter the password or any other credentials on the app running on the device.
The reason I'm making this request is because the primary symptom of the disconnect problems that I and other users are seeing is the fact that the device disconnects with a message that pops up (on the device) which states that its account has expired and a re-login needs to be performed. I believe that this should never happen, once the user properly sets up an account on the device.
Thank you for passing this on to the developers.
The account on the device should never (!!!) expire. In other words, once an account is set up on the device, the device should remember this account and keep it flagged as active forever (!!!), no matter what happens on the device, including exiting from the AirDroid app and including reboots. The only time the account on the device should be expired or deleted is if the AirDroid app is uninstalled, or perhaps during some sort of new, explicit "disconnect" request that the user would have to manually invoke.
If the account expires on the server, I understand that we would need to re-login on the server. However, even in the case of server re-logins, the app, itself, should always (!!!) know what account was previously set up on it, and the app should always (!!!) use that same account during server<=>app reconnection attempts. So if the server session expires and is restarted, the app should be totally ready and fully configured to automatically reconnect to the server, without the user ever having to re-enter the password or any other credentials on the app running on the device.
The reason I'm making this request is because the primary symptom of the disconnect problems that I and other users are seeing is the fact that the device disconnects with a message that pops up (on the device) which states that its account has expired and a re-login needs to be performed. I believe that this should never happen, once the user properly sets up an account on the device.
Thank you for passing this on to the developers.