Strange... Works fine for me. No crash. Tried a few different combinations.
nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug This is the craziest bug I have found in Amethyst. If you search a two characters and an integer, it chrashes the app.
Example: In3, po7, gh0.
Definitely interesting.
Discussion
I believe both Max and I are running on Graphene, might be OS specific bug?
Ahh... I'm on a Samsung.
im on graphene, doesnt crash. what search relays you using?
Nostr.wine, Nostr.band, and noswhere.com. are my search relays.
I'm also using search.nos.today, but I don't think not using that particular search relay is the problem.
Added that relay but still crashes for me. Like I said this is a crazy bug.
This probably a dumb question, but which version of Amethyst are you using? Also, are you using tor via the privacy options screen? I currently have tor disabled.
Version 94.3, I use Tor through Orbot.
v94.3-FDROID?
Yes, but using Zapstore.
I don't think the download source matters as long as it the same version. You should try disabling tor, restarting Amethyst, and trying the search again. Just to rule out tor as the culprit.
No effect, after disabling Tor.
It's still crashing?
Yes.
I'm still thinking it's some FUBAR GOS quirk. GOS has a lot of those. I was just talking to someone about Pokey. He's on GOS and Pokey is regularly waking the screen. Meanwhile, Pokey has never waked my screen, and I don't recall anyone else sharing that issue. But Cloud Fodder was saying he uses GOS and isn't having this crash issue you're having. So I wonder if y'all are using different GOS versions.
i have nostr.wine and relay.nostr.band