I'm hitting exactly this, on a different team, so here's a second case in case it helps show this isn't just one misconfigured project. I uploaded a build in late July, signed with Apple Distribution. App Store Connect validation passed cleanly, no warnings. I submitted it the same afternoon, and the next day got the same automated Guideline 2.5.1 message: the app uses Screen Time APIs but wasn't submitted with the Family Controls entitlement, so review can't proceed. As far as I can tell, it was. Family Controls (Distribution) is approved and Assigned for the main App ID and all four of my extension App IDs, covering a DeviceActivityMonitor extension, a ShieldConfiguration extension, a ShieldAction extension and a DeviceActivityReport extension. The App Store Connect API confirms FAMILY_CONTROLS and FAMILY_CONTROLS_DISTRIBUTION on all five, and all ten of my provisioning profiles (development and App Store, for all five App IDs) carry com.apple.developer.family-controls = true. I also checked the entitlements App Store Connect recorded for the uploaded build itself, rather than just my local archive, and com.apple.developer.family-controls is set to true on the main app executable and on all four .appex binaries. Worth noting I ship a DeviceActivityReport extension as well, so five targets rather than four, and it gets flagged the same way. So this doesn't look tied to any one extension type. Two things I'd love an answer on. Is the automated flag still attached to my app record and holding up reviewer assignment? And if a build gets flagged again, could the message say which binary and which API set it off? Right now there's genuinely nothing for me to fix, since by Apple's own record of the upload the entitlement is on everything. Glad to hand over my Team ID, build ID or submission ID to anyone at DTS or App Review who can dig into it.