Skip to content
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

Reload of Wallet Home screen takes approx 20 sec and routes are not built #21455

Open
mariia-skrypnyk opened this issue Oct 18, 2024 · 2 comments

Comments

@mariia-skrypnyk
Copy link

Bug Report

Reproduction

  1. Install nightly build from 18/10
  2. Create user and reload Wallet Home screen

Actual behavior

Reload of Wallet Home screen takes approx 20 sec and more

video_2024-10-18_10-28-19.mp4

Reload logs.zip

Expected behavior

Reload of Wallet Home screen takes not more than 4-7 sec as it was before

Additional Information

  • Status version: nightly 18/10
  • Operating System: Android, iOS
@VolodLytvynenko
Copy link
Contributor

I encountered the current issue with long wallet loading as well. Additionally, routes are not being built while this issue persists on both Desktop and Mobile. I used the build from this PR where we have a fresh status go, but the issue is also reproducible on the latest master as well

desktop_routes.mp4

Mobile logs:
logs (3).zip

Desktop logs:
geth copy 2.log

@VolodLytvynenko VolodLytvynenko changed the title [Android] Reload of Wallet Home screen takes approx 20 sec and more Reload of Wallet Home screen takes approx 20 sec and more Oct 18, 2024
@VolodLytvynenko VolodLytvynenko changed the title Reload of Wallet Home screen takes approx 20 sec and more Reload of Wallet Home screen takes approx 20 sec and routes are not built Oct 18, 2024
@saledjenic
Copy link

@mariia-skrypnyk @pavloburykh @VolodLytvynenko under no circumstances should you be waiting for the route that long.

I've checked the code many times, and there is no reason for that in the code. However, that part relies on many external things, like providers' responsiveness, network congestion, internet speed, and the performance of the device where the app is running.

In theory when all chains are included in wallet_getSuggestedRoutesAsync call, it should not take more than 20 seconds worst case, usually less than 10.

Also asking the router to generate the route just for a single chain doesn't mean we've solved the issue, but it means, we reduced the number of calls that we're doing, but the time for getting the response is not reduced.

Pretty sure that we can freely say that solving external issues/increasing the reliability of the third parties will solve all our router-related/sending-tx-related issues.

@ilmotta ilmotta removed the high-prio label Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

4 participants