[Namadillo]: animation bug - withdrawing via IBC momentarily jumps to an incorrect network

[zenodeapp]

What happened?

When I withdraw via IBC (shielded), the animation during the process momentarily jumps to an incorrect network. In my case I did an USDC transfer (Noble), but during the transfer it showed an animation of Stride, asset stOSMO and also my stride address. See the screenshots below.

---

1. Initiating a withdrawal

2. Transfer in progress

3. Shifts to an incorrect network

4. Ends correctly

---

I haven't tested this with transparent IBC transfers. But it's plausible that the same happens over there.

Steps to Reproduce

1. Shield Assets
2. IBC Shield
3. Withdraw
4. Select Noble and withdraw USDC
5. See the animation bugging out

Noteworthy is that I'm withdrawing all my USDC + stOSMO is the next shielded asset I have in my balance. Perhaps that gives some insight to why this happens.

Relevant log output

Debug Information

The debug information below shows for some reason the MASP Indexer URL and RPC URL as undefined. I'm just using the default for namadillo.app, so tududes endpoints.

## Navigator
------------------
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/137.0.0.0 Safari/537.36
Screen Resolution: 2181px x 1323px / DPI: 1
Fri Jun 13 2025 18:38:59 GMT+0200 (Central European Summer Time)

## Version Info
------------------
Namadillo Version: 1.26.0
SDK Version: 0.19.0
Keychain Version: 0.8.0
Indexer Version: 3.1.0
Masp Indexer Version: 1.3.0

## MASP Status
------------------
MASP Indexer URL: undefined
Last Shielded Sync: 2025-06-13T16:38:52.841Z
Is Shielded Sync complete? Yes

## Indexer Status
------------------
Indexer URL: 
Epoch: 767
Block height: 2389193
Crawler Info: [{"name":"chain","timestamp":1749832739,"lastProcessedBlockHeight":2389193},{"name":"governance","timestamp":1749832737,"lastProcessedBlockHeight":null},{"name":"parameters","timestamp":1749832737,"lastProcessedBlockHeight":null},{"name":"pos","timestamp":1749832739,"lastProcessedBlockHeight":null},{"name":"rewards","timestamp":1749832739,"lastProcessedBlockHeight":null},{"name":"transactions","timestamp":1749832739,"lastProcessedBlockHeight":2389193}]

## Other Info
------------------
RPC Url: undefined
Account type: mnemonic

[neocybereth]

@zenodeapp have you seen this again and/or are you able to reproduce? We had some code changes to this component recently and I'm unable to reproduce.

[zenodeapp]

@zenodeapp have you seen this again and/or are you able to reproduce? We had some code changes to this component recently and I'm unable to reproduce.

Hey I just tried and it happened again (at a different moment though).

Some remarks:

• I withdraw all my shielded USDC.
• I use NAM for gas payment
• I have stOSMO as my first displayed Shielded Asset (see screenshot).

The first and third remark might be the reason why it jumps to stOSMO?

My shielded assets:

And a video:
https://github.com/user-attachments/assets/a5c99aca-5be0-4262-b96a-95a051986f2b

(Namadillo is version 1.28.2 - used namadillo.app)

[zenodeapp]

UPDATE: I saw this happen at a normal transfer from address A to B as well.

The common denominator is that I max sent an asset. The animation seems to jump to the next asset I have in my balances.

Only sharing this extra info, but I don't consider this an issue of prio to the slightest.

[neocybereth]

Thanks again for poking us. We've got it on the radar it's just not top priority atm but we will certainly get to it!

[zenodeapp]

Thanks again for poking us. We've got it on the radar it's just not top priority atm but we will certainly get to it!

Aah didn't wanna poke by any means! Wanted to add some more data cause of seeing it happen again in another place. Totally get that this isn't a prio at all :)!

[neocybereth]

Thanks again for poking us. We've got it on the radar it's just not top priority atm but we will certainly get to it!

Aah didn't wanna poke by any means! Wanted to add some more data cause of seeing it happen again in another place. Totally get that this isn't a prio at all :)!

🤣 no worries poke is a good thing in this context!