[tbclark3]

Mike, thanks for your thoughtful response.  You are correct that I was not differentiating in my comment between Chromebook native apps and Android apps. I do, however, run several Android apps frequently, including Thunderbird email, remmina, and OpenVPN. None of them has ever crashed and reopened like MobileSheets does. I understand that doesn't prove that the problem is with MobileSheets, and I also understand how difficult it is to debug.  I would be happy to help if you give me some suggestions.

The crash happened again yesterday *while* I was performing in a hymn festival. My music just disappeared in the middle of a verse with a chapel full of people singing.  Yes, from the library screen, I can find the setlist I was playing, which means scrolling, and select it, then select Load All, and it does return me to where I was playing, but about 5 or 6 seconds later--too late to be useful. This flaw makes MobileSheets unreliable, and I'm sure that's not the reputation you want to have.  There are almost 66,000 views of this thread.  It's a huge problem.

If the problem can't be solved, maybe it could be mitigated.  Could you add a selectable feature called something like "Restore setlist and page" so that when the app opens or returns to the library page, it immediately goes to the setlist and page where it was when the app crashed (or closed).  For normal use, such as practicing, the feature could be turned off, but it would be a safety net during performances.  I read a measure or so ahead of where I'm playing, so even if it took a second to restore the page, that wouldn't result in an embarrassing glitch. This app is incredibly well designed, and I can't imagine going back to paper music, but I have to be able to trust my music app, and right now I can't.