nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzpmhxue69uhkummnw3ezumt0d5hszythwden5te0dehhxarj9emkjmn99ue6qm68
Amethyst 1.03.0 is stuck in a crash loop. Can't even get it to stay open long enough to DM the bug report. Can I dig the logs out of my GrapheneOs somewhere and send to your another way?
You might not want to do this, but I don't see how it could be dangerous...
If you go to the application info in your settings, and clear the cache and data, it's like a fresh reinstall. I'm assuming you'll have to re-log in, but if you use something like amber, then that should be trivial.
I think the only thing you would lose is the state the app was in before the crash loop which the only reason you'd want to keep I assume is so that you can accurately report on it but since you can't...?
Yea. Going to see about log dumping to the dev before I clear the app data.
I've been using primal as a replacement
I give Amethyst a pass cuz I think Vitor is a beast and it is feature rich af. Maybe too feature rich but still mostly functional
Some of the other nostr clients seem like the devs never tried their own app once
Open sats and the like need to factor this into who gets grants. A dev like Vitor is more likely to deploy funds appropriately to get reliability up meanwhile others don’t seem to care at all about UX
Hum... Strange.. I can log in with your npub just fine. Have you tried deleting the cache/storage to see if it is a local cache issue?
If not, it might be something that was encrypted by your key and only you can see it :(
Do you have Android studio installed? If so, you can just connect the cable and the logs will be in the LogCat view. It's probably the last block in red.
