status-mobile
status-mobile copied to clipboard
Building routes takes long time if entered value exists on all available networks
Unfortunately, this issue doesn't happen consistently, and there are no exact steps to reproduce it. Hopefully, the logs will help. Discussed this issue here
Preconditions:
The user has assets available on each network
Steps to Reproduce:
- Go to the route generation page.
- Enter a value that exists on your available networks
- Wait until routes are generated
Actual Result:
The route-building process takes an excessive amount of time to complete. (sometimes 2 minutes)
https://github.com/user-attachments/assets/be1ae689-e042-41f0-a452-33c77cb257c7
Expected Result:
Routes should be generated in a reasonable amount of time, regardless of the asset's availability on multiple networks.
Logs:
This issue is related to multi-router. So, it is reproducible in case when wallet_getSuggestedRoutesAsync is used. After implementing the new send flow this issue will gone.
The issue is resolved in the simplified send flow https://github.com/status-im/status-mobile/pull/21595