[Send] got this error on trying to send ETH on Mainnet

[sunleos]

Bug Report

Description

Steps to reproduce

1 .start sending ETH on Mainnet

Expected behavior

the fees are resolved and I can proceed with send

Actual behavior

the fees are not resolved (keep hanging) and I can't proceed with Send

Additional Information

send you logs over email

• Status app version: APK # 8 from this PR: Release 2.38.0 #20630
• Operating System and version: Android 15
• Mobile Device: Samsung S21 Ultra

[glitchminer]

Same issue noted in item 2 here: #20513 (comment)

[saledjenic]

@sunleos @glitchminer do you have steps on how to reproduce this? Cause it seems it's not a constant issue, but more about an unreliable fetching fees process.

[sunleos]

Update:

I don't do anything special, besides starting ETH Send on Mainnet

just tried again and I can reproduce it

[saledjenic]

@sunleos here are some screenshots I took on iPhone, haven't gotten any issues (was setting different tokens to send, amount as crypto/fiat, switched chains, accounts, changed mode mainnet/testned and every time I got the fees and was able to proced with sending).

[saledjenic]

@sunleos I would really like to get the same issue as you. Maybe someone else having android can try, but I don't think it's a platform-specific issue, maybe it's more region-specific.

Apart of the issue, I have to say that the UI/UX is a bigger problem in my opinion, cause nothing is native for mobile apps, mobile friendly. I had a really hard time adding a new account via seed phrase.

[alaibe]

I cannot reproduce either on iPhone or on desktop.Do u have a vpn enabled?

[saledjenic]

@sunleos I asked Andrey to test and he tried on Android, sending ETH and MANA, entering crypt/fiat value and every time he got fees and no issues. I am not sure what's on your end.

Maybe you could create a new Status profile, then go to the Wallet section and add an account (where you have some assets) via seed phrase and then try to run the Send flow for it, and let's see?

[sunleos]

Same issue noted in item 2 here: #20513 (comment)

@glitchminer, can you reproduce it again?

[sunleos]

@saledjenic,

I just reinstalled the app (the same build Status app version: APK # 8 from this PR: #20630)

and now, I can't reproduce the issue.

It seems nearly impossible to nail some particular conditions of this issue.
Maybe any debug logs could be helpful in this case?