+1, same issue here. Reported in Feedback Assistant with ID 13691566 To not let users be impacted by this, you can call startMonitoring again 1 second after you receive the error; this worked consistently for our users, but obviously is a bit of a clunky workaround

After a third attempt it worked for me -- I didn't do anything, didn't delete the app, didn't restart Xcode, but it just started working. Xcode magic we'll call it!

This post might help you: Request the Family Controls permission for your app through the request form Once the entitlement is granted (took about 3 weeks but I've seen varying time frames on the forum), you have to enable Family Controls in your App Store Connects Identifiers section (you only see this option once the entitlement is granted): Identifiers > your_identifier > Additional Capabilities, there you enable Family Controls for App Store distribution. You'll have to do this for all of the Identifiers of your app that use Family Controls, e.g. the extensions etc

+1, same issue. I submitted a ticket to Feedback Assistant to fix this, I suggest more people do the same - this is bad UX for users

So this was actually an issue that took me a while to solve and I want to save others from that pain. The problem is that the Family Controls entitlement only works for development mode, which is why debug releases work fine. For production, you'll have to follow two steps: Request the Family Controls permission for your app through the request form Once the entitlement is granted (took about 3 weeks but I've seen varying time frames on the forum), you have to enable Family Controls in your App Store Connects Identifiers section (you only see this option once the entitlement is granted): Identifiers > your_identifier > Additional Capabilities, there you enable Family Controls for App Store distribution. You'll have to do this for all of the Identifiers of your app that use Family Controls, e.g. the extensions etc

Could maybe have to do with the holiday season?