I'm getting this exact same bug actually. It seemed to happen in our project not simply after we upgraded it from 4.22 (or we simply didn't notice somehow...