-
Notifications
You must be signed in to change notification settings - Fork 987
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
temporary fix for app crash if chat has long ens names #10022
Conversation
Pull Request Checklist
|
What works slow here? have you checked the performance of
If not I would first remove that, and try the ellipsis (as I understand that's preferrable if performance are ok) #10021 . If performance are acceptable then the issue is in Split is not lazy, so it will go through the whole string regardless, if we really wants to keep exactly the same behavior we can use either |
Jenkins BuildsClick to see older builds (3)
|
@cammellos because it works slow only on android, i believe problem in text component on Android, probably it ellipsize every component and its slow, and still its just a simple and quick fix for v1, we must prepare proper fix in v1.1. |
App doesn't crash for me on Samsung J7 (Android 8.1) and Galaxy Note 4 (Android 6.0.1) in status chat with loong ENS (fetched messages and scrolled up to 7th of February morning time history). |
@Serhy try to join #status-chinese and fetch history for 3-4days |
increased length up to 80 |
@flexsurfer with 40 char-long-ens build |
@Serhy and what about #status-chunese in latest nightly or RC ? |
chat still pretty fast with 80 so lets keep 80 |
22c838e
to
2b47f20
Compare
In RC, can't fetch and scroll to the top of 4 days history in |
Signed-off-by: Andrey Shovkoplyas <[email protected]>
2b47f20
to
c1eb986
Compare
temporary fix for app crash if chat has long ens names