@Danny182, Just tested it and it appears to be working.

I was able to figure this out. The AutoReleasePool was basically releasing memory. I had to disable ARC for that file, to get past the error. But don't understand why this would be kicked in by Xcode 13, and why this was never an error in the first place in the previous Xcode versions.

Unfortunately no

Looks like this is fixed as of Beta 5. Anyone else tried it?

@HeoJin Do you know if this works now?

On Beta 4, it shows up on the child device, but not on the parent device. :-/

I can see the list of Applications on the child device after successive requestAuthorization calls. Still can't see it on the Parent device.

@caguilar51 I can see that the picker is loading and showing a bunch of categories, but it doesn't show any apps inside each category. What behavior are you seeing?

Thanks

@jonathancurrie I got this to run by Stopping the monitoring first and then doing the startMonitor.       center.stopMonitoring()       try center.startMonitoring(.daily, during: schedule)     }

@LoguLogu No I've not been able to resolve it. I do see the preview of the categories in Preview screen but it doesn't load on the device.

Thanks for the feedback. I did provide a bug report : https://feedbackassistant.apple.com/feedback/9147978

I tried that out but I am having issues reading from the database. With the Filter Control provider I can open the database as well as read from the database and store the contents. With the Filter Data provider, I can list contents of the App group directory and see that the file exists. I also can open the database, but I am unable to read from the database. I am not even trying to write to the database. This is not the expected behavior from Filter Data provider right?

Thanks for clarifying this. One more question. In the documentation it says the following : Uninstall a System Extension The system automatically uninstalls any system extensions when the user deletes the corresponding app. You can also uninstall a system extension by creating a deactivation request. Call the deactivationRequest(forExtensionWithIdentifier:queue:) method of OSSystemExtensionRequest and submit the resulting object to the OSSystemExtensionManager. When I delete the app it doesn't automatically delete the corresponding System Extension/VPN. Is the documentation wrong or do I need to have done something else for the system extension to get deleted automatically? I can also remove the VPN/SystemExtension by using NEVPNManager's removeFromPreferences. Is there a pro/con in using removeFromPreferences vs deactivationRequest ?

I just submitted a TSI with follow-up number : 745407154, but I didn't see the option to submit the Bundle or the crash logs. What information would you require to further look into this?