Users are logged out of the app every time they close it on their new iPhones.

[david-uhlig]

Description:

Users are being logged out of the Rocket.Chat app every time they close it on their new iPhones.

This issue specifically affects users who have recently switched to new devices. They were able to stay logged in on our self-hosted Rocket.Chat instance without any problems on their previous devices. Now, after they successfully logged in to the instance, then close the app - without logging out, explicitly - they have to log in again when they open it up the next time. Since they are not logged in, they also don't receive any push notifications.

We tried without success

• Explicitly logging out of the account on the old device

The app permissions are identical on both devices.

Environment Information:

• Rocket.Chat Server Version: 6.13.0
• Rocket.Chat App Version: 4.54.1.68xxx
• Device Name: iPhone
• OS Version:

Steps to reproduce:

1. Create a new user account with a iPhone device.
2. Sign in
3. Close the app
4. Reopen the app
5. Confirm you're still logged in
6. On a different iPhone device, possibly a recent one:
7. Sign in
8. Close the app
9. Reopen the app
10. You should land on the sign in page again

Expected behavior:

The user should stay logged in unless they explicitly log out.

Actual behavior:

They have to log in every time they open the app.

[diegolmello]

We tried without success
Explicitly logging out of the account on the old device

Can you try logging out and logging in on the new device?

[Lao-Ax]

We got the same behaviour with our users. But still cannot repruduce on dev env. Re-insalling the app helped for those poor users. But it helps not always. Last time a user had to logout from every session on other places (desktop\web and other devices).

If I find anything - I will share it in this topic.

[david-uhlig]

We tried without success
Explicitly logging out of the account on the old device

Can you try logging out and logging in on the new device?

We did and this worked for one of our users. I assume it works for the others, too, but I have no confirmation from them.