This is helpful for testing and it is what I do. But VMS for the development cycle are difficult to use and not exactly what I prefer.Besides this doesn't change the fact that a tool (tccutil) doesn't work the way it is suppose to.

So I wanted to let anyone know that I figure this out because I have not seen this info anywhere else. In a Sandboxed app, the entitlements, the default config for the File Access has the "User Selected File" set to "Read Only". Changing this to "Read/Write" allowed me to just use the URL directly and append a file name and write to it, without having to use the Scoped stuff at all, which is how it should be.

Hello Quinn, So it turns out this was a problem with a circular reference in a package that we are using. I think that the error message is not clear enough though.

So, it turns out you can simply select the app in the Notifications systems prefs/settings and hit the delete key. I had been trying to right click to get a context menu that might allow me to delete, but that didn't work! So resetting the notifications didn't resolve my issue either, but I will create a new post for that. Scott

Just to be clear, when I get the notificationSettings, it says that the authorizationStatus is authorized!