-
Notifications
You must be signed in to change notification settings - Fork 553
Problem login #2375
Comments
You really need to update your server. You version is over a year out of date and there have been massive changes. v1.1.1 is current |
Same problem here. We're running the server 1.1.1, app version on Android should be the latest one. |
How i can clean app cache and data? I don't see folder like rocket chat in my android. |
You can search the interwebs for generic stuff like this. |
Thank you. It's resolve my trouble. |
Unfortunately this problem is only solved for the OP. We have the same issue, but it keeps reappearing every day. You have to clear the cache, login and you can chat. After a few hours the app says, that "you have to be logged in to do this" and it aparently can't display the server version correctly. So basically you have to start over. |
The beta version 3.5.0 seems to have fixed this to a certain degree. As far as I can tell now, the session is only dropped after the timout which is set on the server (72h for me). It still shows the weird server version sometimes though. But the phenomenon of being able to receive messages while it still complained that you needed to be logged in etc is gone - unless the session is dropped by the server. |
Same problem here. I just joined the beta program to see if this fixes the issue as @aimador suggests. |
Guys, could you tell us if you're facing the problem on the |
I think it's working better for me now. Thanks. |
Same here. The phenomenon of the dropped session is still an issue, but I think it's the server. |
Describe the bug
The app is worked but once contact list is blank and app get error "log in".
Button log out not work.
To Reproduce
Expected behavior
Logs
Screenshots
Devices and Versions
Your Rocket.Chat.Android version: (e.g. 2.1.0)


Ver 3.4.2. 03.06.2019
Your Rocket.Chat Server version: (e.g. 0.63.1-develop)
Mobile device model and OS version: (e.g. "Nexus 7 - Android 6.0.1")
Additional context
The text was updated successfully, but these errors were encountered: