Error after sending assets to multichain address (cannot unmarshal non-string...) about status-mobile HOT 7 OPEN

@status-im/mobile-qa can someone confirm if this issue is still reproducible?

hi @OmarBasem I encountered this error yesterday. I will try to reproduce it one more time and share the logs

from status-mobile.

@OmarBasem seems I found more exact steps. For me, it is reproducible consistently when the arbitrium network is used, but it reproduces on optimism as well

Steps:

1. Recover a user with available L2 assets (e.g., Arbitrum).
2. Open 'account 1' where assets are located.
3. Tap the 'send' button.
4. Select 'account 2' as the receiver.
5. Build an Arbitrum route on the routes generation page.
6. Edit the input value to be slightly less than the available tokens on your account (e.g., if you have 0.01 ETH available, enter 0.0099).
7. Confirm the transaction.

Actual result:

Error after sending assets.

Expected result:

No error is shown.

Logs:

Status-debug-logs.zip

from status-mobile.

@churik I am not able to reproduce this issue. Are you still getting that error?

from status-mobile.

@status-im/mobile-qa can someone confirm if this issue is still reproducible?

from status-mobile.

@J-Son89 considering that announcement on discord should this issue and other issues related to L2 be removed from 2.30 and 2.31?

from status-mobile.

thanks for raising this question @OmarBasem - so L2's should still work.
Going forward we will still be working with L2's, it's just that we won't be doing the multi transaction process.
We will only be doing a single transaction at a time, which could be on any network (mainnet,arb, opt).
Similar for bridging.

from status-mobile.

thanks for raising this question @OmarBasem - so L2's should still work. Going forward we will still be working with L2's, it's just that we won't be doing the multi transaction process. We will only be doing a single transaction at a time, which could be on any network (mainnet,arb, opt). Similar for bridging.

Thanks @J-Son89, sounds good!

from status-mobile.