Update: it *might* happen if I scroll too far after hitting the zap button in Amethyst _before_ the zap finishes sending?
Maybe amethyst is unloading some important bit of information before it hits Minibits? 

 I see. I believe it's not directly related to Amethyst / your behavior.

I've never simulated the issue on pc-connected dev device so I asked people for help with turning on debug level logging on their wallet.

Outcome is that based on various factors, but multiple zaps  processing over longer period of time is a major one - wallet needs to process them sequentionally.

Seems like android is interrupting such longer lasting processes at will, causing the errors you experience.

Working on change that would significantly shorten the processing needed on device, but will take some time.

Until then, there is a fix I've sent in other note. 

 nostr:nevent1qqsdkc8q2vmuenqg7l79ed8nnx9szhvl2vwkyt2u62720dxykqcl3qcpzpmhxue69uhkummnw3ezumt0d5hsyg9n80u7j7mc7dtffgpwdwl03emstymnus4s4pdx8uj62r4lmt04p5psgqqqqqqslq038t 

 Does seem much more stable! And fast!

Thanks!