Nostr Web Client

I made the update to send nip44 encrypted requests by default, but I ran into an issue with the get_public_key

If I start the connection on the client side with a nostrconnect uri and then scan it with either Amber or nsec.app they will send an "ack" response but neither of them will respond to the following get_public_key request.

Amber crashes and nsec.app doesn't say anything 😞

greenart7c3 1y ago

I'll test in the morning. It crashes when you accept the public key or when scanning the nostrconnect uri?

You can check the logs in settings to see if you received the request and if it was a successful reply

Reply to this note

Please Login to reply.

Discussion

hzrd149 1y ago

I scanned the code and it minimizes, then it shows a notification for a request to sign a null event. and when I click on it the app crashes

greenart7c3 1y ago

The error is you are sending get_pubic_key instead of get_public_key

Dikaios1517 1y ago

That's a very different kind of key! 🤣

hzrd149 1y ago

No way....

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

null event cannot be signed, what is this?