-
Notifications
You must be signed in to change notification settings - Fork 12
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
Investigate why Element X Android reports higher UTD count (timeboxed to S) #2591
Comments
Do android x users have a higher chance to also use the legacy android app -> that might affect utd's more than the legacy ios app? |
Scenario to try out:
On iOS, if there is a UTD in the NSE, is it later reported when the app is opened? |
Let's spend 2 days on that now. |
Results of the analysis: For EXI to report an UTD you have to be in the room while the event is received. You can leave the room after and it will be reported. But if the timeline is not opened at the time of reception it won't report the UTD. So if you receive a UTD from a push notif, then you open the app it won't be reported. EXA is reporting more because the app is keeping a LRU cache of recent timelines (up to 16) so if an event arrives in any of these cached timeline it will be reported. Also for performance reasons when android receives a push notificiation it will also trigger a app sync so that you see the event quicker when opening the app, so there is always a timeline for pushed events. => EXA is over reporting because it is reporting UTD that are not visible to users |
Should be:
Right? and
should be
right? |
Come up with some ideas about how to investigate the higher UTD counts on Element X Android.
Possibilities:
The text was updated successfully, but these errors were encountered: