[BUG] Amethyst Crashes when opening an Incorrect Link

[0n4t3]

Hi, appears that Amethyst crashes when opening a Nostr link with an incorrect npub. I tried opening what wound up being an incorrect npub from a browser, specifically nostr:npub106246s. It's probably a pretty low priority bug, since it's not like it's actually going to impair a feature, but figured it was worth cataloging.

Thanks!

Device:

• Phone Brand/Model: Pixel 5a
• Android Version: 14 (GrapheneOS)
• App Version: 0.83.4 (F-Droid)

[vitorpamplona]

Do you have a note or a message where this was crashing? I just tested a few posts with this specific key nostr:npub106246s and it doesn't seem to crash.

[0n4t3]

No specific error or message outside of occasionally saying "Amethyst is not responding", it just closes when I try to open it. The exact steps I can do to make it happen is to go to atomstr.data.haus and add a feed that already exists. When it brings me to the success page and I click "native" link within Fennec it pulls up Amethyst and then it imminently closes.

Could be I misinterpreted what's causing it, it's only the oddly specific chain of events that I've seen cause the issue. Currently on 0.83.12 and still seems to be happen.