This will be fixed in the next app update. I'll add it to the known issues list.