I’ve updated the Namada Wallet, but an old issue has reappeared.
When I tap to synchronize the shielded balance, the app freezes and then crashes - it closes automatically.
The same problem occurs when transferring from shielded → transparent and from transparent → shielded.
Here’s a video demonstrating the issue:
Hello @Quantum-Crypt
did it work on this specific device before?
Yes, it worked without any problems.
Hello @GE.Tnso
The app has more problems. The list of tokens and validators, as well as the results and staking functions, is not displayed. Shielded balance and sync are also not displayed:
Transaction history stopped displaying:
In Governance, only this is currently displayed:
Video showing shielded sync and balance issues:
But in this new section, everything is displayed correctly:
This is an interaction with the Namada Wallet app on a Samsung Galaxy A72 device running Android 14, One UI 6.1. Previously, everything worked and displayed correctly on this device. These errors appeared during the first few days, were then fixed, and have now returned.
Hello, thanks for noticing.
We’re already know about these issues, - connected rpc and indexer have issues last few days and they’re affecting mobile app.
We’ve plans to implement and prepare update with a feature of dynamic rpc, indexer URLs changing to prevent this
ios 26.0.1 . i am not able to see the value to stake. I think stake is not working,
Chain : housefire testnet
App v: 1.1.0(1)
sdk namada: 0.150.1
Mobile sdk lib wrapper : 1.1.0
iOS app is deprecated and we currently cannot upload new version in App Store, because of Apple’s policies. We estimate resolve it at the end of this month.
if you interested in iOS testing, I just can add you to Test Flight. Via TF we can distribute new iOS versions only for invited users [we need user’s Apple ID to send invite].
Today we’ve released version 2.0.0
Improvements:
Updated! Transparent balance is now showing again after the update, but the shielded balance still fails to sync - it hangs and crashes the app:
Governance is now visible again after the update:
The transaction history is still not displayed:
Version and configuration:
Problems on nodes:
Review of Namada MASP Indexer Nodes (2025)
Several public MASP indexers were tested:
→ Returns “Resource Not Found” on /api/v1/status, but Swagger docs confirm API structure. May still work for balance queries.
masp-indexer.namada.stakeup.tech
namada-mainnet-masp.itrocket.net:443/api/v1
namada-mainnet-masp.mellifera.network/api/v1
All returned:
{“error”:{“message”:“The requested resource does not exist on this server!”}}
Conclusion:
As of November 2025, no stable public MASP indexer is accessible. This is a known issue - indexers are community-run and often go offline after upgrades (e.g., Phase 4 migration). Some validators report needing snapshots or URL changes to restore service.
Today during testing, I changed the RPC URL, Indexer URL, and MASP Indexer URL, but the Chain ID cannot be modified. After switching nodes, the wallet visually completes synchronization and displays Shielded token entries, and Transfer Transparent-to-Shielded, Shielded-to-Transparent also syncs correctly. However, transaction entries are now displayed incorrectly, and Transparent tokens (other than NAM) are non-functional:
Adding the ability to change the Chain ID is required for full functionality.
Further, I noticed another bug/glitch: when switching from one account to another within the same application, non-existent balances were temporarily displayed (the same incorrect value across all tokens), which then disappeared, showing zero balance everywhere. Most importantly, the wallet does not display the Luminara reward amount or its transaction history, as if the transaction never occurred.
Screens:
Hello @GE.Tnso ,
Thanks for this new app version !
These are my test details:
Pixel 6A
Android 16
App version: 2.0.1
Staking completed successfully; however, I received a misleading feedback message indicating a “broadcast commit” error:
Shielded and unshielded NAM transactions have worked correctly.
As mentioned above, I successfully shielded NAM, but I have never seen the updated shielded NAM balance in the wallet (Shielded → Home), even after multiple shielded syncs. (This screen displays “0” for my shielded NAM balance.)
Note: My NAM shielded balance is correct in the “Unshield” screen.
I installed the Leap Mobile Wallet on my phone and funded it with USDC on Noble, but I wasn’t able to connect the wallet.
I received the connection request, then a “connection failed” message.
The deposit features look promising, and the privacy notices are a great addition! 
However, before moving forward, I’d like to see improvements to the overall user experience and fixes for the issues we’ve already identified, especially:
Thanks for the work so far.
I’m available if needed, and have a great day!
Now this time I’ve restored the standard nodes:
This time, synchronization succeeded on the first attempt, but fake and non-existent amounts that I didn’t deposit are displayed only in NAM and USDC, and upon reopening the wallet or returning to Shielded Tokens, the balance is 0 again:
Also, my actual balance is slowly becoming visible in the Shielded balance, but it does not appear in the transaction history:
Then synchronization started failing repeatedly, increasingly so with each attempt, showing the following errors:
In this menu, synchronization stopped; I monitored the network traffic and then noticed that incoming and outgoing connections had completely halted, while the app still displayed an ongoing synchronization process:
Conclusion: In these last two tests, the app itself did not freeze or crash. Only the shielded synchronization stalled and disconnected. Overall, the issue is that shielded synchronization stops, disconnects, and does not fully complete.
Hello, thx for feedback.
Today we released 2.0.2 with a few improvements:
This update already feels better - synchronization of the Shielded Pool and Transfer from shielded to transparent completed faster and on the first attempt. However, there are still bugs and glitches displaying false or non-existent amounts for other tokens:
And this is after the second synchronization:
The shielded balance is only displayed in “Transfer: shielded - transparent,” but the balance does not appear in “NAM Shielded Tokens,” and there is no transaction history either:
Subsequent attempts again showed synchronization and display errors, and the Shielded Pool would freeze (the synchronization process became endless) in the app - sometimes traffic flowed infinitely, sometimes it stopped completely. A similar issue occurs in Transfer, where synchronization continues indefinitely with either unbounded traffic or a complete halt:
And most importantly, the key request is to add the ability to modify or manually enter the Chain ID in the Account → Network Configuration section. This would allow me to conduct even more testing, and overall, in the long term, provide greater functionality and flexibility in the application for all users.
is the new update only for Android ?
Interesting, ok I’ll look deeply in shielded balances issue a little bit later.
I think in a future we’ll add functionality to change chain id, explorer URL.
Yeah, deposit screen should be redesigned and polished, seems buggy now.
btw, we’ve merged something new in the version 2.0.3
should be deployed ~ in a few hours.
After the update, the first two shielded pool synchronizations and two transparent-to-shielded transfers (without revealing addresses) completed successfully, quickly, and without any issues. However, the NAM balance was again incorrectly displayed, but on the third attempt it appeared to reset to zero:
The transaction history is still not being displayed:
After some time, I ran the shielded synchronizations again, but the synchronization froze, stopped, while internet traffic continued indefinitely. The Transfer Shielded synchronization got stuck at this point:
In addition to implementing Chain ID switching, it is strongly recommended to integrate an external namada-masp-indexer for stable and fast Shielded Pool scanning. This indexer acts as a block explorer, similar to Blockchair API for Bitcoin, but designed specifically for Shielded NAM.
Direct chain synchronization is highly resource-intensive and slow. To improve performance, the wallet should connect to a running instance of namada-masp-indexer, either locally or over the network.
Connection example: http://localhost:5000/api/v1
Benefits:
Significantly faster scanning of shielded transactions.
Reduced device resource usage.
Stable operation under frequent queries.
@GE.Tnso, are you planning to add Namada Wallet to the F-Droid and Aurora Store repositories to support installation without Google dependencies or verification?
