Nostr Archives

There are reports that users installing Minibits on Android from Github and Zapstore are not getting over-the-air wallet updates. I therefore released a new cumulative update of current native version including all OTA updates as an APK package to Github and Zapstore, tagged v0.3.4-beta.19. Please check the version you are running in Settings > Developer options: 👉 if you still run old release 0.3.2-beta.x, please update immediately, there were important bugfixes released over time in 0.3.4. This is valid for all users, including those that use Google Play. 👉 if you run 0.3.4-beta.8 or beta.11 and you are not offered OTA update in Settings > Update manager, please check Github or Zapstore and upgrade to the new version ✌️ if you run 0.3.4-beta.19, you are running the best Minibits out there. Enjoy!

💬 36 replies

Replies (36)

Henkypenky☢️46d ago

Updated, but in developer options still showing 0.3.2-beta.14

0000 sats

Minibits46d ago

Do you see NFC icon in the top right corner of the main wallet screen?

0000 sats

Henkypenky☢️46d ago

0000 sats

Minibits46d ago

Then it's still 0.3.2 📝 b2743a20…

0000 sats

Minibits46d ago

I you are using Zapstore, check if there is an update again, I've re-published the release events.

0000 sats

crany 👽🧡🗿46d ago

Not seeing 19 in ZS...

0000 sats

Minibits46d ago

Indeed, I see the same and more, the update is failing to download. When I check release links on web https://zapstore.dev/apps, those are updated and I can download the package from @78ce6faa…f026307d CDN without issues. Sorry for troubles, but for now do not know what's wrong.

0000 sats

Hypno | seedkeys.xyz46d ago

I uninstalled the app I had from the playstore. But I can't install from Zapstore. I get this:

0000 sats

Minibits46d ago

I've retested that and indeed have the same result. Not sure why, because I can download the APK from both Github and Zapstore CDN without issues. Here is the APK published on Github that Zapstore downloads when publishing new release: https://github.com/minibits-cash/minibits_wallet/releases… Here is the link to Zapstore CDN download: https://cdn.zapstore.dev/01a40098cec0e5eff3cf570752c356da… SHA256: 01a40098cec0e5eff3cf570752c356daabdbffc31536fa9cca162ce83dabee5b Sorry for troubles not sure why it's not downloading from Zapstore app, links on thir web https://zapstore.dev/apps are updated and pointing to the new release.

000

Maciek46d ago

Hi, I love minibits wallet and I use it all the time. I've uninstalled the play store version, installed the latest from GitHub and now I'm trying to recover my wallet from backup, but I'm getting the following error. What do? 🤔

0000 sats

Minibits46d ago

Looks like the backup string was cut off somewhere on the way. Check if you copied the whole string, starting with minibitsA... If nothing helps, use your seed to recover full balance using the seed-based balance recovery. Sorry for troubles, backup could be in less error-prone format.

0000 sats

Minibits46d ago

If you see similar troubles to our fellows below with upgrading from Zapstore, and prefer not to use Play store, you can use direct downloads for the timebeing the issue with Zapstore is resolved: Here is the APK published on Github: https://github.com/minibits-cash/minibits_wallet/releases… Here is the link to Zapstore CDN download with new version: https://cdn.zapstore.dev/01a40098cec0e5eff3cf570752c356da… SHA256: 01a40098cec0e5eff3cf570752c356daabdbffc31536fa9cca162ce83dabee5b

0000 sats

33a0b70…926dab45d ago

Hello :) Seems there are few troubles with inputs during recovery using the 12 words seed phrase on Android in 0.3.4-beta.19: Blank spaces are deleted as soon they are entered. You can work around it entering for example an undescore "_", then type words separated by a blank space, and finally remove the "_". Still this leads to an "invalid seed phrase". This happens both in recovery from backup or recovery drom seed options.

0000 sats

33a0b70…926dab45d ago

This means that, after uninstaling a previous version and updating to "0.3.4-beta.19", on Android, you may be unable to recover.

0000 sats

Henkypenky☢️46d ago

Still the same, no change from zapstore dev.

0000 sats

Minibits46d ago

Hm I wonder then if it's the update itself on your device that is failing. You might try to clean the table without going through the balance recovery as follows: 1. Backup seed and send your balance to another ecash wallet (like web based cashu.me) 2. Uninstall then install from direct link (github or zapstore cdn, I've tested both) 3. Start the wallet, move balance back 4. Go to Settings > Recovery > Seed recovery > Wallet address and use your seed phrase to get your former wallet address back.

0000 sats

Henkypenky☢️46d ago

Uninstall, reinstall from zapstore helped.

0000 sats

Hypno | seedkeys.xyz45d ago

Thanks. I downloaded and checked the file. Then, installed it. But my backup doesn't work to recover. It says: VALIDATION_ERROR Invalid backup: JSON Parse error: Unexpected end of input. If I only use my seed to recover, it finds about 50% of my eCash... So, I'm missing 50%... Any idea what I should do now?

0000 sats

Minibits45d ago

Yor wallet likely contains ecash generated using older mint keyset. After recovering what you have now, still on recovery screen, choose Select keyset at the bottom of the card. Then select previous keyset starting 005... and go through necessary recovery intervals again to get the second half of your balance.

0000 sats

Maciek46d ago

I don't think that's the issue. I've tried it with a different backup and got the same result. Is it possible that there's a conflict between versions? I didn't write down the mints I was using 😶

0000 sats

Maciek46d ago

And I've lost access to my custom address.

0000 sats

Minibits45d ago

Thank you for your report. I could simulate the issue, the validations to prevent seed failures because of wrong chars sneaked in are a little too aggressive. Until then there are few good options: - copy / paste the seed, do not write it in - if you need to, write two seed words together and then put space in between, to avoid spaced at the end of seed phrase that are auto-cleaned.

0000 sats

33a0b70…926dab45d ago

Thanks for the explanations. I tried the workarounds in beta 19 and just tried copy-pasting in beta 20. It still returns an invalid seed (I'm sure 1000% of the words and their order). Writing the words and handling ending blank spaces indeed worked in beta 20. I guess seed failures preventions included also other types of spaces like new lines or tab from GUI. Thanks again!

0000 sats

Hypno | seedkeys.xyz45d ago

Thanks. But it didn't work. I get: Recovery failed Wallet keyset has no keys

0000 sats

Hypno | seedkeys.xyz39d ago

Do you think that Ecash is lost forever? It's not much, but I'd rather get back my 4,000 something sats...

0000 sats

Minibits39d ago

Please try the recovery again and make sure you are on the latest 0.3.4-beta.23 version - there was a bug that should be fixed now.

0000 sats

Hypno | seedkeys.xyz39d ago

I tried the 5 keysets, and intervals until 500 for each. But I found only 4 sats. I'm not sure where I'm supposed to look. Keep going after 500?

0000 sats

Minibits39d ago

Ok the big is gone. After each round, wallet announces if ecash has been found - for longer wallet histories, there is spent ecash first, that is filtered out. How far it goes until unspent is found depends on the history of the wallet being recovered. If nothing is found for 3-4 intervals it is safe to assume there is none. Only two keysets matter for wallets not older then a year: current 001... and prev 005... You need to be sure to use correct seed - e.g. if you reinstalled rotated to a new seed, that one will link only tge ecash issued from there on.

0000 sats

Hypno | seedkeys.xyz35d ago

OK, I did that today. Had to go until 2,850 until I reached 4 intervals with nothing 🙃 But I got all my ecash back. Thanks! Do you think that this process could be automated? Because it's a hassle. Also, I didn't know what to check and until when. It wasn't a lot of money, but still, a bit stressful when what you had seems to be gone.

0000 sats

Minibits35d ago

You're right it's not optimal for few reasons: - you've hit a combo of a bug and long history - unfortuntely on mobile device the recovery ops take few secs for each round - fresh wallet nor mint can't know where the unspent is, unless we know the last counter values (you can check them in mint screen before you reinstall and set the starting point in Minibits - if you do not deal with device loss that can help). I have some idea on how to make complex recoveries much easier. Will think of it more.

0000 sats