smb big sur

[quote='769161021, Bhavyekhetan, /thread/769161, /profile/Bhavyekhetan'] Can … NEDNSProxyProvider … be used for on-device filtering? [/quote] Yes. Although you’d usually use a content filter for this. But, and this is a big but, both of these providers have significant deployment restrictions. See TN3134 Network Extension provider deployment for the details. [quote='769161021, Bhavyekhetan, /thread/769161, /profile/Bhavyekhetan'] Would pre-configured safe DNS (e.g., CleanBrowsing) be acceptable? Are there compliant examples of similar apps? [/quote] I don’t work for App Review and can’t comment on their policies. If, after reading TN3134, you decide to start down this path, I recommend that you raise this with App Review directly. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m not entirely sure what you’re asking for here, but it sounds like you’re trying to be notified when the user locks and unlocks their iOS device. If so then, no, there’s no API for that. You can listen for the UIApplicationProtectedDataWillBecomeUnavailable and UIApplicationProtectedDataDidBecomeAvailable notifications to learn about the state of data protection state, but that’s not the same thing. I’ve seen folks try to use various unsupported techniques for this. My advice is that you not go down that path. As with all implementation details, they’re subject to change without notice. Why do you need this info? If you can explain more about the big picture context, I may be able to suggest an alternative path. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

One of it's options is skipsSubdirectoryDescendants, which lets you disable recursion. But then I get a shallow enumeration. I still want to scan an entire directory hierarchy. I know, but you can still use NSDirectoryEnumerator. What you do is: Shallow enumerate the current directory. During that enumeration, collect the directories you find. Repeat from #1 using the directories you find in #2. In other words, you do a shallow enumeration of a given directory, then repeat the shallow enumeration on whatever directories you find. This is actually the same thing you'd do with getattrlistbulk. The copyfile Unix API will let you do that but the Finder isn't using that either, which is why the Finder can do server side SMB copying, which copyfile cannot I've noticed that, which is why I've been using copyfile for a long time now myself. Have or haven't? How are you copying files? FYI, if server side copying is an issue, this post has a code snippet for that. In terms of why the Finder isn't having issue

Lemme me be clear about one big picture point: DTS doesn’t support folks re-signing .ipa files. From our perspective, the format of an .ipa file is not documented for third-party use. The technique we recommend instead is to have your developer’s submit an Xcode archive (.xcarchive). You can then export a .ipa from that archive, allowing Apple to take care of all the re-signing complexities. If you need to automate that, xcodebuild can do it via its exportArchive command. Still, it’s certainly true that a lot of folks do re-sign .ipa files. IMO this is Working Too Hard™ and they should just change their process. Clearly there are other opinions (-: But the unsupported nature of this task explains why you’ve been having such a hard time finding definitive answers about it. We generally don’t document unsupported processes. If you are committed to this re-signing .ipa approach, the place to look for answers is the Mac code signing documentation, because DTS does support code signing by hand for Mac pro

Hey huge thanks for responding and sorry for being late I missed it! OK. A couple of comments: 1 - Your last comment, it's not accurate. In our app, we have Lock Screen widgets. They are visible at the same time and it looks very strange that they do not get updated when the live activity does. If you do it from the Dynamic Island and have a widget below on the Home Screen, you can see it there too. This is a big reason to why we think it's so bad. 2 - It's not really an issue if the widget being updated 5-10 seconds, or perhaps even 30 at times. However if you run my example app you quickly see that often the widget isn't updated at all, even hours later. 3 - This happens a lot. We have been running this for weeks, and we quickly get in to situations where the widgets aren't updating for hours or for the rest of the day even though the live activity has been updated over 50 times. Again, always works in Xcode. To me, it's clear that this is not a battery or prioritization issue because it happens co

One of it's options is skipsSubdirectoryDescendants, which lets you disable recursion. But then I get a shallow enumeration. I still want to scan an entire directory hierarchy. The copyfile Unix API will let you do that but the Finder isn't using that either, which is why the Finder can do server side SMB copying, which copyfile cannot I've noticed that, which is why I've been using copyfile for a long time now myself. In terms of why the Finder isn't having issue I think you misunderstood. I said that the Finder is having the same issue.

So, let me start with the error here: ls: fts_read: Permission denied fts (File Traversal Stream) is basically the Unix/POSIX equivalent to Foundation NSDirectoryEnumerator. The details are documented in it's man page (man fts), but fts_read returns the next file system object in the iteration set. So Permission denied would mean you weren't able to read the contents fo that directory. Moving to here: The problem is that I get permission failures trying to delete certain directories. How were you deleting the directories? What actually failed, particularly in relation to the directory you're trying to list? After this happens, if I try to list the directory using Terminal on the 15.1 system, I get a strange error: Do you get the same failure if you open a new terminal window an navigate to the directory? Do you get the same failure if you unmount and remount the SMB volume? What do you see if you list the contents of the parent directory? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thanks for your detailed response. Flattening sounds like a good idea, although I'm a little bit reluctant to adopt it since this would likely mean that if one day I switch to FileManager.default.enumerator(at:includingPropertiesForKeys:errorHandler:) the bug would appear again (unless it has been fixed in the meantime). Nah, you can do exactly what I've described with enumerator(at:includingPropertiesForKeys:errorHandler:). One of it's options is skipsSubdirectoryDescendants, which lets you disable recursion. The user just confirmed to me that when copying the folder in the Finder, the same looping issue occurs. So I was wondering: wouldn't FileManager.default.enumerator(at:includingPropertiesForKeys:errorHandler:) (which I assume is used by the Finder) profit from using iteration instead of recursion as well? No, it's definitely not using that. If you pay attention to exactly what the Finder does when copying files and the functionality provide by NSFileManager, you'll pretty quickly realize that NSFileMana

Same issue since upgrading my machine to Sequoia. I'm following the guidelines from the Chromium browser (https://www.chromium.org/administrators/configuring-policy-for-extensions/) in order to try to set some custom policies for my web extension. I've tested on both Sequoia & Big Sur, and Sequoia seems to be the only affected version.

The lack of native Docker support makes me want to transition to Linux. I really hope Apple will add native Docker support. Colima (Homebrew / brew install colima / colima ssh / ~/.colima/default/colima.yaml / docker cli works from Mac Terminal) works but getting the shares and folders to work correctly is a real hassle. With vz the disk sharing works, with qemu the SMB shares work.

I disagree with your assessment that this is kind of how HTTP cookies work. The RFC you link is for how a server needs to interpret a cookie sent to it not how a client should implement creation of one. I think others would likely agree that this is a wart and that setting secure to false would result in the correct behavior of not setting the secure attribute on the cookie. It also make coding something simple like .secure: environment().isSecure() into another if statement that every person coming after will question why it's done this way and then eventually figure it out. The only reason I agree that this likely needs to stay the same is it's a pretty big breaking change at this point and many apps are likely working by accident as setting .secure to anything other than true makes no sense. Anyway... wasted more hours than I would like to admit on this as I was also adding a new networking library as well as adding cookies to the app so I spent a lot of time debugging the new library when it was

I’ve boiled your example down to this: @globalActor actor MyActor { static let shared = MyActor() } @MyActor protocol ProtocolMyActor { } @MyActor func make(value: String) -> any ProtocolMyActor { fatalError() } @MainActor class ViewObserver { init() async { let implementation = await make(value: Ciao) // ^ // Non-sendable type 'any ProtocolMyActor' // returned by call to global actor // 'MyActor'-isolated function cannot cross // actor boundary print(implementation) } } The issue here is that there are two isolation domains: make(value:) is isolated to your custom global actor, MyActor. ViewObserver.init() is isolated to the main actor. You’re trying to send a value (the resulting any ProtocolMyActor value) between these two domains, but that value is not sendable. There at (at least :-) two ways you might fix this: If types conforming to ProtocolMyActor must be sendable, you can make that a requirement of the protocol: @MyActor protocol ProtocolMyActor: Sendable { } If you don’t want to add that requirem