have helped with feedback and testing as nostr:nprofile1qqsy8us3d6u5ynddk7lq7yz365hqqsptzd2923fvkgj4eepsady08uspzemhxue69uhkzarvv9ejumn0wd68ytnvv9hxgqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46q4cv2tf builds it out
definitely early but very promising
Discussion
Thanks for the clarification. Definitely promising.
I was particularly impressed with Cove's integration of the different test coin networks. I wish more wallets similarly gave test coins the respect they deserve. I can only wonder how many precoiners are scared away from a self-custody wallet (or bitcoin altogether) just because they don't feel comfortable jumping right in without being able to practice first.
I’ve been working on the android version, but after that there will be more regular releases.
What are you missing most in it?
If memory serves, I was having trouble exporting a psbt file (so that I could sign it from within sparrow wallet). First, trying to communicate with sparrow via QR wasn't working; but, I couldn't tell if that was a problem with Cove, Sparrow, or me. So, I tried exporting the psbt file instead (to either Signal or the iPhone Files app) so that I could then import into Sparrow; but Cove failed to export the file to either.
To be clear, this was all just in testing, so to say I'm "missing" this specific functionality would probably be a bit of an overstatement... but it seems like basic enough functionality that I lost interest in trying to find out what else I could break. I do look forward to giving a thorough beating to the next iteration, though, as long as it seems like it's up to the task. 😉
That sounds like a bug that shouldn’t happen, I haven’t run into it, are you on the version from the App Store? If so if you could try it again and DM me maybe we could figure it out. That would help me out a lot. Thanks for the feedback.
I'd be happy to try to help... it may be a day or 2 before I'm ready to, though.
It was definitely from the Apple App Store. When I'm ready, I'll make sure I can repeat it again, and let you know. And, assuming I can indeed repeat it, I figure it's probably best if I just log an issue on your Github? (I'd be using the same handle)... then we can continue our troubleshooting from there?
PS. I considered logging an issue on your Github to start with, but I figured it was so obvious you would have it fixed by the next release anyway, so I decided to just wait (I guess maybe it turned out not to be that obvious after all).
Sounds good thank you! GitHub issue works. I think it might be some sort of edge case cause you’re the first to report on it. And I haven’t run into myself.
I was able to get to it today after all; and, I was indeed able to repeat the problem. Here's the link to the issue in I logged in Github. All do what I can to help you figure it out; and I'm looking forward to hearing what makes it an edge case; but otherwise, good luck! 😉
BTW, I doubt there's anything you can do about it, but it looks to me like someone's mining your Github issues looking for a sucker they can 'help':