not sure what i did that made it work, because a) i filled out more things in the NEFilterProviderConfiguration(), and b) tweaked the entitlements to add the group to the main app (see diff)
still getting sad error of "this won't work on a production app, just letting you know you're bad and should feel bad"
tried os_log-ing from the extension code. couldn't see the logs anywhere
tested which extension class (control or data) was blocking, was data (x.com was blocked, not apple.com), but (see below vvv)
quitting and restarting console.app seemed to sorta restore connection
(update:) reattaching with Debug > Attach to process (in xcode), plus restarting console.app got me my os_log messages. (it might also have been that i added an env variable to the Run scheme, following this to address a warning i got in xcode console)
(update2:) i think maybe i have to NOT be attached in XCode for this to work? also i turned on "include info" and "include debug" in the Action menu of Console.app
future ideas
try on a "supervised device" (maybe our iphone 15?) a kids? what does this even mean?
try to see os_log on ios (maybe there's an app for this?)
jaredh159
commented
2 weeks ago
NEFilterProviderConfiguration(), and b) tweaked the entitlements to add the group to the main app (see diff)os_log-ing from the extension code. couldn't see the logs anywhereos_logmessages. (it might also have been that i added an env variable to the Run scheme, following this to address a warning i got in xcode console)Actionmenu ofConsole.appfuture ideas
try to see os_log on ios (maybe there's an app for this?)