nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz8rhwden5te0wdshgetvd35hgefwdpa8yep3xsujucm0d5hsqgpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg55la0jnz there was an upgrade to nip46: https://github.com/nostr-protocol/nips/pull/1248#issuecomment-2437731316
Seems like Nostrudel is not auto-decrypting nip04/nip44 when receiving nip46 replies, so current nsec.app stopped working.
Also don't forget to make a get_public_key call to get the user pubkey as it can be different from the uri
Oh that's a different upgrade, but yes. To work with the new FROST signer (create at start.njump.me) you'd need to create a new variable to store signer_pubkey (from bunker url) and after the connection is established call get_public_key to discover the remote user pubkey.
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 😞
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
