-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal bug - Android v. 11 (Samsung Galaxy S20+) - after upgrade on weekend (10-11. April 2021) #3069
Comments
Hello, Thanks for help, Lubomir |
We have also experienced the issue. Setting the language to English in the profiles of the affected users seems to be a workaround. |
This workaround unfortunately is not working for us. |
Steps to reproduce our workaround:
We use LDAP authentication and our affected users had two factor authentication turned off. |
How can we reproduce this issue? |
Our affected users had the Hungarian language set up before the workaround. |
The bug was introduced probably on this PR #3014 |
Ok, I might have got it. |
Building 4.16.1 |
It's live on Google Play. Requesting review on App Store in a bit. |
We have working mobile apps now! Thank you. |
Dear Rocket.chat team,
we've been upgrading our Rocket.Chat client this past weekend (10th - 11th April) and unfortunately uncountered critical issue in the mobile client. I'm using Samsung Galaxy S20+ and the Rocket.chat client 4.16.0.
I've been unable to successfully start the client as it seems to freeze on the Rocket.Chat logo. The client only start if I clear cache and data first but this "fix" helps only for a single use, once I close the client and try to start it again, the issue reappears.
I've also discussed this with my colleagues and they encountered exactly the same issue on various versions or even different OS (ie. Android 11 or even iOS with the latest update), so this is not an isolated issue bound to a single device. Seeing the latest feedback on Google Play, I'd say that this is not even an issue with our company settings as many other users seem to be experiencing this issue.
Thank you in advance for investigating this.
Kind regards
Filip Langer
Linux support L2
NETHOST s.r.o.
The text was updated successfully, but these errors were encountered: