Nostr Web Client

not receiving / processing nip46 requests

on device signing work great with Amethyst and NoStrudel.

signing via nip46 isn't working (at least on v1.0.6).

it's unclear whether Amber is not connected to relay.nsec.app (an indicator would be nice) or it is failing to process nip46 events properly. either way it doesn't respond to requests.

I love Amber and discovered this when adding nip46 support to ngit.

greenart7c3 1y ago

Are you using the push notification server or direct connection?

Are you receiving the notifications?

I added a log screen and some messages when sending the response but didnt release a version yet

Reply to this note

Please Login to reply.

Discussion

DanConwayDev 1y ago

I'm using the default (push notification server) but having just changed to direct connection, and I get the same behaviour.

DanConwayDev 1y ago

Amber immediately opens on the signing page when I try and sign an event in Amethyst. Otherwise nothing appears in the notifications . Changing it to 'direct connection' there is a permanent 'Amber is running the background' notification.

greenart7c3 1y ago

Are you using the free version or the play version?

DanConwayDev 1y ago

free version

greenart7c3 1y ago

Did you install ntfy? Can you check if it's receiving the events there?

DanConwayDev 1y ago

I actually have amber installed on two devices. One of which had ntfy and was receiving notifications from amethyst. Same nip46 on both devices.

greenart7c3 1y ago

Try this beta https://github.com/greenart7c3/Amber/releases/tag/v1.0.7-pre2 and let me now if if works

DanConwayDev 1y ago

Yes! I can confirm that it works in v1.0.7-pre2 and not in v1.0.6. I even downgraded to double check.

This event was signed through nip46 in that version.

Thanks very much for fixing it.

DanConwayDev 1y ago

Note: it didn't work if a secret was included in the bunker URI

greenart7c3 1y ago

Yeah the secret is not implemented in some applications