Explicit Content Not Allowed ENABLED - but still able to see explicit content

[josephali1]

Hello,

We've had content filtering enabled on all of our students iPads. We had a case where explicit content was seen via search on Safari. The interesting thing is that this same configuration profile is pushed to multiple iPads, but its not being applied to all of them. It shows as pushed and active configuration profile on the device, the restriction is visible under Profile > Restrictions. 

1. iPad #1 is iPad 5th gen on OS 14.4.2 and the configuration profile works as it should. Searching for the term "Sexy" gives the restriction notice. 

2. iPad #2 iPad 9th gen on OS 17.4.1 and the configuration profile seems to be ineffective. Searching for the term "Sexy" shows explicit content. 

I've gone through and compared the other configuration profiles to see if there is any discrepancies, to no avail.  

What could be causing this issue? Why is the content filtering being applied to one device but not the other? We are dealing with this scenario on a much larger scale. 

[yaksha]

There are a few reasons why the content filtering might be working on one iPad but not the other, even though the configuration profile shows as active on both. Here are some possibilities to explore:

1. Differences in iOS version:

You may want to check Apple's developer forums or release notes for iOS 17.4.1 to see if there are any known issues related to content filtering.
2. Profile payload malfunction:

It's possible that the specific payload within the configuration profile responsible for content filtering might be malfunctioning on some devices. Here's what you can try:

Remove and Re-push the Profile: Try removing the configuration profile from the problematic iPad (#2) and then re-pushing it from your MDM (Mobile Device Management) solution. This can sometimes refresh the profile installation.

Check Payload details: If you have access to the MDM solution used to push the profile, double-check that the content filtering payload settings are identical for both iPads. Even a minor difference in the payload configuration can lead to unexpected behavior.

3. Conflicting profiles or restrictions:

It's possible another profile or setting on the iPad is overriding the content filtering restrictions. This could be another MDM profile or a local restriction set directly on the device.
Review other profiles: Look for any other configuration profiles or restrictions on the iPad that might be interfering with content filtering.
Check Local Restrictions: Go to Settings > Screen Time > Content Restrictions and ensure these settings are aligned with your desired content filtering level.
4. Safari settings:

While less likely, there's an outside chance that a specific Safari setting on the non-filtering iPad might be bypassing the restrictions.
Verify Safari Settings: Go to Settings > Safari and ensure settings like "Suggest Search" and "Search Engine Suggestions" are disabled if you want stricter content filtering.
5. MDM Supervision Level:

If you're using an MDM solution, some advanced content filtering features might require the device to be "supervised".
Check Supervision Level: Review your MDM documentation to see if "supervision" is required for the specific content filtering features you're using.