Hello @DTS Engineer ,
We are developing and try to deploy app based content filter aswell. Facing same issues as mentioned in this thread.
I am using Intune to push a custom provision profile with
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PayloadContent</key>
<array>
<dict>
<key>FilterBrowsers</key>
<true/>
<key>FilterSockets</key>
<true/>
<key>FilterType</key>
<string>Plugin</string>
<key>PayloadDescription</key>
<string>Configures content filtering settings</string>
<key>PayloadDisplayName</key>
<string>Test content filter</string>
<key>PayloadIdentifier</key>
<string>com.apple.webcontent-filter.DAC44B5F-3824-4F6C-B39B-1C5FCDD8C993</string>
<key>PayloadType</key>
<string>com.apple.webcontent-filter</string>
<key>PayloadUUID</key>
<string>DAC44B5F-3824-4F6C-B39B-1C5FCDD8C993</string>
<key>ContentFilterUUID</key>
<string>DAC44B5F-3824-4F6C-B39B-1C5FCDD8C993</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>PluginBundleID</key>
<string>Replaced the original name here</string>
<key>UserDefinedName</key>
<string>Test content filter</string>
</dict>
</array>
<key>PayloadDisplayName</key>
<string>per app content filter example</string>
<key>PayloadIdentifier</key>
<string>Replaced.EB0E51A5-84B0-49AA-B45B-9EA8C46C69FE</string>
<key>PayloadRemovalDisallowed</key>
<false/>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>AEDDCA4D-392B-49E5-801B-D9D4E34BAA30</string>
<key>PayloadVersion</key>
<integer>1</integer>
</dict>
</plist>
and in my content filter trying to use NETestAppMapping in info.plist
<key>NETestAppMapping</key>
<dict>
<key>DAC44B5F-3824-4F6C-B39B-1C5FCDD8C993</key>
<string>com.apple.mobilesafari</string>
</dict>
The profile is pushed to the device
It shows the network filter as invalid
Tried creating a DTS ticket aswell. It asked me to first check in developer forums
Post
Replies
Boosts
Views
Activity
Hello,
I see similar crashes for /bin/sh and some of the other apps aswell. When I verify the code signature of the disk is fine and the application runs as expected if manually it is started after the OS has started.
But when the applications are run as daemon using the launchctl and when the machine is rebooted I see it crashes with the same CODESIGNING 4 Launch Constraint Violation error.
Where you guys able to figure out what was wrong in your case?
Thanks & Regards,
Prasanna