FamilyControls App Blocking Not Working for External TestFlight Testers

Question

HamzaK4 OP

Created May ’25

Replies 3

Boosts 0

Participants 2

Hi everyone,

I'm following up on this post I made earlier about an issue I'm having with FamilyControls and the DeviceActivityMonitor extension not working for external TestFlight testers.

To briefly recap:

I have official Apple approval for the com.apple.developer.family-controls entitlement (distribution)
The entitlement is added to both my main app and the DeviceActivityMonitor extension
The App Group is correctly configured for both targets
On internal TestFlight builds, everything works as expected: app blocking works, the extension runs, and selected apps are shielded.
On external TestFlight builds, users get the Screen Time permission prompt, can select apps to block, but nothing is blocked.

Since that post, I submitted a Code Level Support request, and Apple asked me to file a bug report via Feedback Assistant. I did that almost a month ago.

The only reply I’ve received since is that they can’t give a timeframe or guarantee it will be resolved. I'm stuck in limbo with no updates and no fix.

This feature is critical to my app and I cannot launch without it. I’ve reached out to other developers who use app blocking, and none of them have run into this issue. My setup seems correct, and Apple has not said otherwise.

If anyone has experienced something similar, found a workaround, or knows how to get real movement on a bug report like this, I would really appreciate any help. It’s been weeks, and I just want to launch my app.

Thanks so much.

Boost

Answer 1

DTS Engineer OP

Apple

4w

Apple asked me to file a bug report via Feedback Assistant. I did that almost a month ago.

What was that bug number?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 2

DTS Engineer OP

Apple

4w

The bug number is FB17441507.

Thanks.

You’ll receive this message via your bug report soon, but I might as well pass it along here too…

To start this investigation we need a sysdiagnose log taken on the affected device shortly after reproducing the problem. Please attach that to your bug report.

For more about sysdiagnose logs, see our Bug Reporting > Profiles and Logs page. For general hints and tips on bug reporting, see Bug Reporting: How and Why?

ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.

You should receive

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0

Answer 3

HamzaK4 OP

3w

Thank you for updating me. I really appreciate it.

I have sent over the relevant sysdiagnose from an affected test user's device in the bug report, shortly after reproducing the issue as requested.

Interestingly, the feature has now started working for some external TestFlight users. Previously it was not working for anyone. I have not changed anything in the setup, so it is unclear what triggered the improvement. That said, it is still not working consistently across all devices.

Thanks for the guidance too! :)

0