-
Notifications
You must be signed in to change notification settings - Fork 501
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
Regressions in 1.3.0 #4202
Regressions in 1.3.0 #4202
Comments
Thanks @thibaultamartin for the report. We are on it. |
I noticed an odd pattern: it looks like push notification keep making it through, but it looks like the rest of the interface model is frozen. It is possible to navigate in the interface itself, but it looks like the model (i.e. the new incoming messages, the message count changes) is not updated. |
You are right. The root cause of those issues are models in the app that do not update. We are missing a UI refresh somewhere. |
element-hq/element-ios/issues/4202 The start locked the `asyncTaskQueue` forever preventing next call of resume from resuming the sync stream
Describe the bug
There seem to be several regressions on Element and 1.3.0 on iOS. I couldn’t find reliable reproducers yet, but in the first 30min the following happened at different times, and after killing the app several times:
To Reproduce
I couldn’t find reliable reproducers, it seems to happen randomly in the 10min after the app was killed.
Expected behavior
Messages and typing notifications being sent and displayed in real time
Screenshots
N/A
Smartphone (please complete the following information):
Additional context
Not much else. Congratulations to the teams for the gorgeous new designs, the UI is really slick. Good luck chasing those bugs, you’re doing great work!
The text was updated successfully, but these errors were encountered: