Thanks for reporting this issue, and the solution! I’ve patched the code and tested it. I could not reproduce your issue, but I can verify that your change is certainly not going to do any harm, so I’ve added it along with a test that should have (but as I said) did not reproduce the issue 🙂
This should be in the next release in a few days.
Do you play Magic?
Get TopDecked MTG, the #1 Magic App, built by players, for players. Free to use, forever.