I have reproduced this behavior after a reboot.
Well, good news is that we know what's going on, bad news is that Google intentionally made things a lot worse for us than I thought... Why the hell would they even implement something that's affected by whether you've rebooted since you updated the app?
Well, good news is that we know what's going on, bad news is that Google intentionally made things a lot worse for us than I thought... Why the hell would they even implement something that's affected by whether you've rebooted since you updated the app?
