This is a known issue in the latest Classic app update. Of the reports I have seen, all of the users seeing this had not yet gone through app migration and their locations aren’t eligible for migration at this time. Internal investigation is ongoing.