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.
@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?
@jonathancurrie
I got this to run by Stopping the monitoring first and then doing the startMonitor.
center.stopMonitoring()
try center.startMonitoring(.daily, during: schedule)
}
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?
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.
@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?
@jonathancurrie
I got this to run by Stopping the monitoring first and then doing the startMonitor.
center.stopMonitoring()
try center.startMonitoring(.daily, during: schedule)
}
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?