I got a continuous series of nip04_decrypt failed: invalid base64, using @Clave
Maybe it’s a good idea to have some exponential backoff/throttling when the signer fails? I’m sayng that because Clave relies on push notifications to work and boy, my phone did not have a good time when I logged in and the errors started coming through.
Login to reply
Replies (2)
Exponential backoff won't fix Clave's dependency on fragile push notifications, a relic of Google and Apple's stranglehold on mobile.
Looking into it.
I wouldn't be able to test with Clave, so once an update is out, try again and see if things improved.
(btw how is Clave? I got someone asking me for iOS signers to recommend)