This may not be a bug with the SDK necessarily, but I was able to reproduce it on at least a couple Season 1 games (e.g. Omaze, Questy Chess) after noticing it on the game I’ve been developing, so I decided to create this thread to at least discuss.
When you open and close the menu, whatever the game was showing is “saved” behind the menu, i.e. a game doesn’t have to redraw it when the menu is closed. But if you lock the screen while the menu is open, when you unlock the screen, it resumes the game but does not redraw the previous frame. If a game selectively redraws only parts of the screen, this leaves the screen messy with some new graphics drawn on-top of the menu that was still in the framebuffer.
So you can reproduce this screenshot by opening Omaze, then pressing MENU, then LOCK, then LOCK (again, maybe 2x, to unlock). After that, opening and closing the MENU doesn’t fix it - you have to exit the game or otherwise trigger a fullscreen redraw.
I’m not sure if this is new, I didn’t notice it before now but I’m not sure I’ve specifically tried that sequence of actions before.
I assume it’s possible for a game to work around this by redrawing the whole screen itself whenever it’s unpaused, but I’ve been engineering my code around partial redraws so that would require some redesign if I were to pursue that approach.
but when I get it repaired). 
