I think can be that I had the backup on your Jumble fork that had spark integrated, so when I restored the backup on zap.cooking, gives this error?
Someone tested created the backup on zap.cooking and restoring on zap.cooking and worked ok.
Discussion
I did test earlier by restoring a relay backup from a different client and it worked for me, but might warrant further testing. This is definitely an edge case.
Thanks, I think we’ve got it solved! There’s no bug in nos2x, it was just a lack of detection method for the older wallet format created by the previous app. Bug was on our end.
I still reproduce the same problem.
It hasn’t been merged yet.
OK, the fix has been merged and tested.
I created a new wallet with the Jumble Spark prototype using the Keys.band extension, which does not support NIP-44 encryption, so the backup was encoded using NIP-04.
I then switched to nos2x to decrypt and restore the same wallet using Zap Cooking, and it worked as expected.
Your relay backup should work now.
