YWallet technical support

I’m experiencing the same issue as well. It had been working fine until a few days ago, but now the same error is occurring in YWallet on all of my computers (a total of three).
Is this a problem that I cannot resolve on my end?

The problem is that YWallet/Zkool are not yet compatible with the latest Zcash (NU6.1) update that was activated yesterday. That is why this error appears.

You should wait for the wallets to be updated.

1 Like

Just FYI for everyone it’s not only with sending. I am unable to receive ZEC, at least into a newly created account/address. Sent from exchange, transaction shows up on chain explorers, but nothing in my Ywallet account although it does give the id consensus error repeatedly.

The update was pushed about 2 hours ago. The versions on the app stores will follow in the next few hours, likely.

3 Likes

There are issues with the android version because of “new” requirements on app published on the Google Playstore. It will take some time to sort them out.

3 Likes

I get this problem, too. Same issue as Hardaeboria.

2 Likes

(post deleted by author)

@hanh I’m also having issues with the flatpak (just downloaded it from your github). When I run it from the CLI I get:

ywallet: symbol lookup error: ywallet: undefined symbol: g_once_init_enter_pointer

I noticed that flatpak info me.hanh.zwallet.Ywallet | grep Runtime
gives me Runtime: org.freedesktop.Platform/x86_64/22.08

But 22.08 is EOL. I’ve updated my version to 24.08, but I still get the same error when running Ywallet. However I don’t know enough about flatpak to tell if it’s my installation, or if there’s a packaging bug and the latest version of Ywallet still declares its runtime as 22.08 but is built against something newer. Previously, I just downloaded the flatpak and installed locally and everything was seamless. Running on Debian.

Any suggestions?

1 Like

I am still stuck in Ywallet mobile, before my zcash stored in bitpie,but it isn’t working now, they decided to stop supporting zcash network. I am trying to restore my wallet, it doesn’t work. they suggest me to use sweep tools. It shows that no enough funds for the transaction fee,but I do have zec in my wallet,both onchain balance and wallet shows that. The reason is utxo and new zip technology, I need extra zec to pay the transaction fee . So who can help me to figure it out? It is weird.

1 Like

My Ywallet app on iphone / ipad / macos still says “invalid consensus branch id”. Please help.

apple store hasn’t reviewed the update yet
.

1 Like

Hello. I had received transfer in Zcash in ywallet as Transparent. When I try to withdraw it, it is saying the following Errors on the pictures. I am sending to other Transparent address and it is not working since the last 24 hours. Any recommendation how to withdraw the funds from that wallet to other Transparent address, where I can exchange it for other currency?

See above thread, you will need to update the app.

GitHub - hhanh00/zwallet at 77428aa99cebc826096bc2d9fb6ba39823223775

So I should download the ZIP file and then how to open ywallet. Is there a guide or if you can just write me the steps quickly ( I download for the first time from GitHub sorry ) ? Thank you in advance!

@Shawn Hello. I had downloaded it from here (the ywallet.zip file only) by clicking on it on other pc. The showing version it is 1.14.0 +564/77428aa9 I could not restore the walled with seed phrase from the other pc ( older version ywallet ) as the wallet account did not appeared. I went to “ Sweep”, filled the seed phrase, selected Transparent and another Error. Check the picture. What do I do not correct? Pleae help me. @Autotunafish

1 Like

This is an error coming from the lightwalletd server. You can try another server or just wait a bit. It happens from time to time. @emersonian

1 Like

Hello. I had been trying for the last three days and does not work. Only this error after “Sweep” to the new version on other computer. Anyone that has figured it out or can I use other wallet to upload the seed from ywallet and withdraw from there without these “Errors”? @hanh @Shawn

Upgrade to 1.14.x