-
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
Some iOS 16 phones do not save session #5268
Comments
We didn't receive any reports regarding this issue. |
I have at least one Person on Ios16 with stock rocketchat App that reported similar behavior on 4.45. Login on every app use. Server-Admin confirmed the user has multiple valid sessions, so the server doesnt exclude them from using a session. |
@b90g Do you have a rough idea of how many iOS users you have there? Do they have different Rocket.Chat roles, or different iOS settings, etc? |
thanks for bringing this back to my attention. one user is on IOS 17.3.1 the other one on 16.x Users might have custom roles but no admin. Login is SAML via KeyCloak. Overall users is a few K, but just heard from about 2 Users from the "phenomena" but since its different versions and our app is RC stock not white label, i rather open a separate issue/request? |
No need. Let's focus on this one until we have more info. @sanyappc is it still happening to you? |
@diegolmello yeah, I still have to use custom mmkv as there is no way to get everyone to reinstall the app |
How sure you are by this point? 😬 |
today another person contacted us, the number of IOS users is unknown, since its a lot of volunteers who bring their own device. but its only IOS users so far. |
it works
exactly, I also changed the name of the DB in |
Description:
We have updated our white-label app from version 4.35.1 (or 4.27.1) to version 4.40.0 and now after closing the app users are forced to login every time.
We found two solutions:
I think the problem is that our users upgraded the iOS 16 first and only then we released a new version of the app and ran into the problem of changing the default accessibility level (and there) or just because of new accessibility level. So we had to migrate the data.
We've changed two files, but we're not sure if that completely solves the problem.
Can you please tell me how to solve this problem completely?
Environment Information:
The text was updated successfully, but these errors were encountered: