mirror of
https://github.com/status-im/status-react.git
synced 2025-01-12 03:54:32 +00:00
9f245ceb30
Fixes the slow login when users have joined large communities, such as the Status one. Related status-go PR https://github.com/status-im/status-go/pull/5229. What we mean by "slow" is that the user was getting stuck on the login screen for almost 20s in some devices (even on iOS things were bad). And this entire process was happening in status-go, hence most changes come from there. By "login" we mean the process to authenticate and initialize vital data in status-go. Setting up message filters can be slow with large communities, and that's exactly this part we moved out of the login phase in status-go. This step now happens implicitly when the client calls wakuext_startMessenger. In a way, the solution makes sense because setting up filters isn't essential for the user to access other parts of the app, such as the Wallet, Settings, Profile, and Activity Center. How can we magically eliminate the login delay? In reality, the time we used to spent during login, blocking the user, still happens, but it happens in the background and after the user is redirected to the home screen. This also means that, until the filters are established, all chats are still in their "loading skeleton state". In terms of UX, this is probably fine as long as it doesn't take too long for this setup to finish in status-go. In the future, we have room to further optimize how filters are set up in status-go. Fixes https://github.com/status-im/status-mobile/issues/20059
10 lines
339 B
JSON
10 lines
339 B
JSON
{
|
|
"_comment": "THIS SHOULD NOT BE EDITED BY HAND.",
|
|
"_comment": "Instead use: scripts/update-status-go.sh <rev>",
|
|
"owner": "status-im",
|
|
"repo": "status-go",
|
|
"version": "v0.180.30",
|
|
"commit-sha1": "b665d68d0cff7cd4521ac8791fcf6eac29b23cd9",
|
|
"src-sha256": "1bpj3x2bmrh7whhx9sb2wgwc4q8knm4c3rzvimp0s84fsvna5ynq"
|
|
}
|