Oddbean

nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck, I'm working on finalizing the Amber integration for nostr:nprofile1qqs2xugc5jyguqkj36rk0syv4tmnkjdtmtperttl7x9rqjy3ustdcvcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg6waehxw309aek2mnyd96zumn0wdnxcctjv5hxxmmd9uxa0uz8, with the last thing needed being the decryption methods (NIP-04 and NIP-44). For the life of me, I can't seem to get them to work. I've put in the encrypted text with and without the iv value and the hex pubkey of the sender and receiver; regardless of the combination of those that I use, it always comes back with "Could not decrypt the message". Do you have any idea of what I could be doing wrong? The messages are properly encrypted, sent, and decryptable on other clients, btw. #asknostr #dev

I've developed a plugin for CapacitorJS that works with Amber and other NIP-55 Android signers, you might find some answers in there if you're stuck: https://github.com/chebizarro/nostr-signer-capacitor-plugin

Guess: Decryption tricked me once in ndk because sender and receiver pubkey namings can be confusing. You always need to decrypt with providing the recipient pubkey(p-tag) and the PEER pubkey. This "peer pubkey" could be your user (your user sent a message) OR another user (p-tag refers to YOUR user as recipient and someone sent your user a message). I had to check which is which to get it right.

> the hex pubkey of the sender and receiver I guess that sender is OK but receiver should be their privatekey, right? refs: https://github.com/nostr-dev-kit/ndk/blob/d2c323cbb3563d8ccb7e9cd8ff658473362efeb1/ndk/src/signers/private-key/index.ts#L137