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 😞

Reply to this note

Please Login to reply.

Discussion

I pushed the update to the next version if you want to test https://npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez.nsite.lol

You can enable the debug logs in the console with `localStorage.debug="*"` and look for the logs that start with NostrConnectSigner

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

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

The error is you are sending get_pubic_key instead of get_public_key

That's a very different kind of key! 🤣

No way....

null event cannot be signed, what is this?