So this actually does appear to be a known issue that the team is already addressing here:
Allow some time for this fix to land in the release build.