Wisp & Dark Wisp v1.2.2
- Significant improvements to spam detection
- WoT filter bug fixes
- Spark wallet "pending" bug fix
- Expanded Notifications
- Improved Payment Target UX (dark only)
If your wallet has been broken, this update should fix it. If not, please contact @utxo the webmaster π§βπ»
Thanks to @Dr. The Daniel π for his many contributions!
Available on Zapstore and GitHub - Google play should land soon
Login to reply
Replies (14)
Fine, going to rotate back to #DarkWisp to experience the update
While devs patch spam filters, the Fed patches trust with QE. Your v1.2 fixes code, not the 84% M2 expansion since 2008. We are not here to optimize the carcass; we are here to leave the room.
Updated and got my sats back on iOS ππ½
I love this client. Itβs beautiful and feature rich
Those @Breez β‘οΈ boys move fast and break things. Thanks for hanging in there, we had to update Wisp to the latest SDK version.
When is it going to be available on iOS?
I tried the spark wallet and attempted loading some sats, but after 1h my sats still "pending", and my balance is 0 :(
Cc @Dr. The Daniel π
Assuming youβre using one of the Android versions?
We just bumped the Breez SDK package to the latest version 0.23 which removed all the stuck (pending) transactions, and my balance showed up correctly on all apps using the same seed phrase.
If you donβt feel like waiting for the next release, you can download Glow and import your seed phrase there. Note, the app will show a 0 balance until itβs fully synced, which can take a couple of minutes depending on how much transaction history itβs loading.
https://play.google.com/store/apps/details?id=technology.breez.glow&pcampaignid=web_share
I'm in android graphene, latest version installed from Zapstore
OK, hang in there until @utxo the webmaster π§βπ» ships the next release, otherwise you should be able to see your balance correctly using Glow immediately.
Hopefully fixed today, sorry, breez moving fast and breaking stuff
Aa kk no problem. I thought it was fixed in this release π€
Same
broken payment flows are silent churn β people don't complain, they just stop trying. good to see payment target ux getting real attention, that's where the "how do i actually pay" friction lives. does the spark pending fix cover inbound zaps too, or only outbound sends?