smb big sur

[quote='803177022, Andrewfromvictoria, /thread/763405?answerId=803177022#803177022, /profile/Andrewfromvictoria'] I feel like this is a yes or no question. [/quote] I admire your optimism. I’m not aware of any scenario where we’ve shipped a consumer Mac [1] where the root volume was formatted to be case sensitive. OTOH, Apple is a big company with a bazillion products so I can’t give you the guarantee you’re looking for. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] It wouldn’t surprise me if we did it for some server configurations, back when that was a thing.

The final solution: This site was helpful: https://blog.arrogantrabbit.com/ssl/Root-CA-macOS/ Create a Certificate for our local development Using the Certificate Assistant to first create a Root CA for the computer Jacaranda (store in System) Using the Certificate Assistant to create a leaf Certificate for the domain xpedite.local (store in Login) Trust the certificate authority. Export the certificate authority to local-cert using the .cer format. I'm creating Jacaranda.cer We can drag and drop this RootCA .cer file onto the simulator to install it. Inside the simularor you can check in Settings | General | About | Certificate Trust Settings to ensure it has been installed. Export the leaf certificate to local-cert using the .cer format. I'm creating xpedite.local.cer You will be prompted for a password, I'm using '***********' Export the leaf key to local-cert using the .p12 format. I'm creating xpedite.local.p12 You will be prompted for a password, I'm using '***********' Run the commands: openssl x509 -i

Thanx @Vision Pro Engineer Michael, I did follow your suggestion and filed a feedback report that apple may add this for the users to know the progress of loading the big 3d Models so far I guess most of the progress bars I have seen in other apps are dummy and not really accurately showing the loading progress of the model rather a timer with some random values or a timer with a delay bar evaluated by the developer him self and it might be different on the user real device.

Thank you a lot for response! Starting with the bottom line question first, the big question I'd ask here is what you're actually trying to block and why. I'm not sure there is any good way to block everything at the USB layer and unless you that's REALLY what you want. The customers wants to have such possibility in DLP system. Criteria to block is device properties ( e.g. productId, vendorId etc.) I found solution which is based on USBDeviceReEnumerate() and it alows to unplug the device. ( see 'https://developer.apple.com/forums/thread/741051'). That post is an excellent example of what makes this area so frustrating. That post is basically asking I've just detected a mount request in my ES client, how do I prevent the mount. That question has an obvious answer. If you want to block I/O to a block storage device, you can do so by: Denying mount in your ES client. Denying open to the device node in your ES client. At that point the mass storage device cannot be accessed from user space. Adding USB

locationServicesEnabled() has everything to do with authorization. If the user disables this setting, your app will not able to receive authorization, and if it has been authorized before, it will lose that authorization. You only need to check this if your app cares and can do something about why it does not have authorization. You can always just check .authorizationStatus and decide on your next steps if it is not important to know 'why'. It may seem like just a setting, but it is a synchronous call that needs to go out of your process to check that setting, and that is not an atomic action. Meaning, your main thread will block while it is waiting for a response. Whether it is a big issue or not depends on your app. It may matter to you if you are playing video, streaming real time data, or gaming. Or you may not care if your app mostly sits idle at your UI. Hence it's a warning you may heed or ignore. Argun Tekant /  DTS Engineer / Core Technologies

Hi, I created Feedback Post, it has FB15025859 I'm really curious about your response, solving this issue would be very helpful for upcoming new features for our player-environment for a very big audience in germany.

Thank you a lot for response! Starting with the bottom line question first, the big question I'd ask here is what you're actually trying to block and why. I'm not sure there is any good way to block everything at the USB layer and unless you that's REALLY what you want. The customers wants to have such possibility in DLP system. Criteria to block is device properties ( e.g. productId, vendorId etc.) I found solution which is based on USBDeviceReEnumerate() and it alows to unplug the device. ( see 'https://developer.apple.com/forums/thread/741051'). However, using USBDeviceReEnumerate() leads to looping because the system tries to plug the device again and again. Are there any way to avoid this looping? Is it safe if application constantly calls USBDeviceReEnumerate()? Strictly speaking, it is possible to block USB devices through the IOKit stack. You an use either of those user clients to obtain exclusive access, at which point no one else will be able to communicate with the device. Thank you! It so

NSTextLayoutManager.usageBoundsForTextContainer gives me a wildly inacurrate (much too big) height, and enumerating the documentRange.endLocation Y coordinate in reverse gives me a too small height. Any workarounds for these issues yet? I can't get any reasonable/reliable text height estimation from NSTextLayoutManager. And enumerating in a forward direction is not possible, since if you have lets say 10000 lines, this will destroy performance for a non-contiguous text view since we are always forcing layout of the complete text.

I have this case for more than 4 days, I sent EMail and called Apple Dev but they do not care about my problem. It is sad for a big business, but they ignore small customers.

Hi, What is the easiest way to implement such blocking? Starting with the bottom line question first, the big question I'd ask here is what you're actually trying to block and why. I'm not sure there is any good way to block everything at the USB layer and unless you that's REALLY what you want. Looking at a few specifics: Looks like IOKit does not allow to block USB (at least in user space) The issue that comes up with IOKit is that many of our drivers (including USB) exit the kernel at multiple points. Typically, that means some combination of: -One more more userclients at multiple levels of a given driver stack. On USB, there's a user clients against the IOUSBHostDevice itself, then (typically) one or more IOUSBHostInterface user clients. -Depending on the actual device, the exit out of IOKit may be through a non-IOKit interface that isn't really visible through IOKit. For example, mass storage volume end at an IOMediaBSDClient, which leads to the dev node and then DiskArbitration volume mounting

Hi Apple, Thanks for your reply, i tried to use withUnsafeMutablePointer and the crash disappeared. but we did not figure out the root causes: Why it crashed when building with Release configuration and using Xcode15.3 or newer Xcode versions including Xcode beta 16.1? Why it does not crash when building with Release configuration and using Xcode15.2? Why it does not crash when building with Debug configuration and using any Xcode versions? Why it does not crash if it goes into an extra logic if isUsingCharFilter is true? for more detail see If we do not figure out the root cause described above, it has big risk. cause it maybe a bug of Xcode15.3 and newer Xcode versions. Please help to figure out, thanks for your help.