Nostrum does not shows the Connect URI the first time
badonyx opened this issue · comments
Nostrum is the reference signer implementation for Nostr Connect. Is there also a reference client implementation?
The only implementation of Nostr Connect that I am aware of is in the mobile web app for snort.social but I was not able to get it working with Nostrum on iOS. When I copy and paste the code into Nostrum and press "Approve" nothing happens. Is it a problem with the client or the signer?
If there are other client implementations please share them here.
Did you checked the example client that uses the JavaScript SDK? There is also a live version linked in there
https://github.com/nostr-connect/connect/tree/master/example
Thanks. I tried the live demo by scanning the code with the iOS app and it does not seem to be working. It accepts the code but then it just goes back to the main screen still saying "Nothing yet" and the webpage still says "Disconnected".
Did you try again a second time to scan in the same session? For some reason, I also encountered a bug which scanning the QRCode the first time does not trigger, but doing it again will then work 🤯
Will try to debug it soon.
Same problem. Multiple tries. No connect. Following.
I tried scanning multiple times. It accepts the code and prompts to "Reject" or "Approve" for "example.com". Pressing "Approve" does nothing while pressing "Reject" dismisses the prompt. Maybe it just needs the correct URL?
On Snort I do not see the option for Nostr Connect anymore, maybe they removed it.
I found this app to be very unreliable, so i wasnt able to test is completely, yes the NIP-46 button was removed in the new signup flow, you can see an old version of snort here which still has it: https://a842e4e1.snort-social.pages.dev/
I found this app to be very unreliable, so i wasnt able to test is completely
Thanks Kieran @v0l. Maybe with your assistance, @tiero will be able move forward implementing nip-46 on a working client in the wild? (Not much to play with in this space)
Y'all both smarter than me. All I know is that nip-46 native app is essential to the future of nostr PWAs. How can I help?
Apologies guys, bit busy moment for me now at work. Nostrum never meant to be production ready, but I must absolutely need to find the issue, be it on a relay, the app or the connect SDK. I will try to find time this weekend 🙏
It was a React state issue. It seems now to be fixed, let's on Testflight once it gets approved.
Feel free to test from master the latest commit on a deceive of yours
It seems to be fixed on the latest TestFlight, thanks for reporting.