Game Loss After I Assigned Blocker Order And Timer Ran Down-- Android Client
I attacked with a suspected skeleton token. Opponent blocked with two creatures. I assigned blocker order.
Expected behavior: It is now my opponent's time to decide things. If the timer runs out, that's on them.
Actual behavior: Timer runs down. Match informs me that if I don't make a decision, I'll forfeit. However, I've already made a decision, and I don't have any option to make another decision.
Systems note: This is perhaps not the ideal failsafe for when a timer runs out? From what I can recall in a few other situations, at other times when the timer runs out, the game just moves on to the next step. This is not always ideal and doesn't stop the initial bug wasting both player's time and eating through timers, but it does at least stop a bug from inevitably being a straight up game loss.
This is on the android app, which had a "save log" button, which I clicked on a few times, but this didn't actually have anything to paste? Maybe you see it on your end, unsure how that system works.
Lost my last game in a draft due to this, which really sucks-- I mostly just don't want to run into this issue again, but if you're able to recompense, that'd be appreciated.