Popping Sound

I just found that you can just log in with your snadbox account when the login request is popped up in your app which has a in-app purchase. Then you also can find sanbbox account menu in the Settings > Users and Account. For just a record.

Hey everyone, I found a solution. I tried deleting the files app. Then I airdropped myself several files at once. It popped up on my ipad asking me where to put the files, and I could drop them into forscore immediately.

error 00:47:00.954979+0100 kernel Sandbox: BookmarksBench(61956) deny(1) file-write-data /Users/user/Documents/file which reminded me to check the entitlements – turns out I forgot to specify read/write access for user-selected files... Fixed that - and everything is good now. Thank you. Yes. The type of access a bookmark will allow is embedded at creation, so you can't use NSURLBookmarkCreationWithSecurityScope unless you already have read/write access from the sandbox. However, one slightly odd detail is the words from words sandbox. The sandbox and Unix permissions systems operate independently of each other, which means you can create a NSURLBookmarkCreationWithSecurityScope (read/write access) to an object you only have read (Unix) permission to. Your app still won't be able to access that object (because the Unix permissions will block it), but it would be able to access it in the future after the Unix permissions change. PS. Quite interesting that that affects secure bookmark creation, but not normal b

Thanks for writing about this. It sounds like what you are experiencing could be a bug. Please file a report using the Feedback Assistant tool with these details about your experience including a screen recording of you trying out the selection behavior with and without VoiceOver. https://developer.apple.com/bug-reporting/ After you create your report, reply here with the Feedback ID so I can take a look

It sounds like a large number of directories have been blocked - i.e. all of them. Or are these blocked target file prefixes rather than directories? Looking at my previous post, our editor mangled things a bit. Phrasing things a bit more plainly, document-scoped bookmarks can't track files in /Library (either the system or user level), /private/, or .ssh. None of those are directories I'd expect the user to be saving their data in. I could see /Library being a potential problem, however, that doesn't seem to have been much of an issue in practice since this is the first time I've ever noticed the limitation (and that was simply from looking at code). That's better than the error message it throws now. But I'm a bit confused about your object/target nomenclature. Sorry about that, I flipped my terminology mid-post. Restating things: target” -> the file you’re actually creating a bookmark to. anchor” -> the file you're attaching the document scope onto. So your anchor can be wherever you want, b

Scratch this there’s nothing wrong with the sounds and haptics

You do have to add com.apple.security.files.bookmarks.document-scope to your entitlement file yourself, Already done. The object you're using as the bookmark anchor needs to be a file, not a directory, and must be a file you already have full read/write access to. Already done. The object you're targeting needs to be a file as well. That's an important plot point. My current app looks at folders exclusively. So that's all I tested. Document scoped bookmarks are designed to be used to track groups of user files (for example, like an Xcode project), so a small number of directories have been blocked. It sounds like a large number of directories have been blocked - i.e. all of them. Or are these blocked target file prefixes rather than directories? Ah well, such is life. I'm working an an iOS/macOS GUI version of a command-line GIS tool. I had wanted to allow the user to specify a directory to be used as a library. Power users could then use my sandboxed and Metal-powered version of the command line app

The alert field (it is actually a JSON key containing a title, body, and sound keys) is used to alert a person about a critical Live Activity update. When included in the payload, it will light up their device (if appropriate) and display the expanded presentation on devices that support the Dynamic Island or a banner on devices that don’t support it. Its content DOES matter, as without any text or sound, it is basically a silent notification, and its behavior in the context of live activities is undefined.