smb big sur

Bonjour et bienvenue sur le forum. No, don't submit again. Your app will remain in rejected status during the investigation. Don't worry, it will clear as soon as the inspection is completed (or you'll get a message). It could take several days for this investigation.

Lemme take a step back and ask about the big picture. Why are you doing this? Why do I ask? Because my experience is that folks get into multicast for two reasons: They’re implementing local network service discovery, in which case it’s much easier to use Bonjour. They think it’ll be a performance boost, which is often not the case. My Wi-Fi Fundamentals post explains why. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for bringing this issue to our attention. To better assist you, we'll need a bit more information: Xcode Version: What version of Xcode are you experiencing the crash in? macOS Version: Which version of macOS are you running? (e.g., Ventura, Monterey, Big Sur) Reproducibility: Have you been able to reproduce the crash reliably? If so, could you please share: A screen recording showing the steps leading up to the crash. A detailed list of steps to reproduce the issue. The more information you can provide], better. Can you also share the crash file? Have you filed for an FB number? Can you share the FB number on this post for other people who are having the same issue? Otherwise, please report it using the Feedback Assistant. Don't forget to include the crash file, reproducible steps, and if possible, the project that is causing the issue. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bu

Hope you enjoy it and the Creator by the way Ryan this message and yes I am nine in fourth grade and this means that kids in all ages to make big changes and sometimes if you chase your dreams, it will always work out for you and the Lord will be following every step also never worship the devil he will give you internal pain instead worship God with him. He will love you and you will love him, and you’ll be happy in heaven. (&) Also, this means that I’m the creator (/)

Thanks for the reply. I have filed a report and attached a project to repro it. It's a big enough deal that I also started a paid support incident (so far I've only received confirmation). Report is FB15492822. The incident case ID is 9640471

A customer of mine reported that since updating to macOS 15 they aren't able to use my app anymore, which performs a deep scan of selected folders by recursively calling getattrlistbulk. SO, my immediate question is why are you calling getattrlistbulk? There was some value in it when it was originally introduced, however, it's well enough integrated into our higher level APIs APIs that I can't really see any reason why you'd use it. The correct NSFileManager APIs are just as fast, far easier to use and, most important in this case, more likely to correctly handle weird edge cases that cause it to fail. I actually posted some performance testing on this issue, but the basic summary is that with a LOT of work, testing, and you MIGHT be able to get SLIGHTLY better performance out of fts (in my testing, 0.2s when iterating a set of 350,000 files)... but nothing that comes CLOSE to justifying all of the extra work. Note that I didn't specifically test gattrlistbulk because the three APIs I compare there are ALL wr

Hello Quinn, Apple’s frameworks tend to use lazy initialisation, ... Thank you for that detail. That (and the rest of what you note in your answer) addresses my curiosity. Taking a big step back, the standard way to get the macOS version from the command line Noted. Although in the context of where this issue shows up, the command line way of determining the OS version isn't applicable for us. For context, this unexpected log message got reported as a bug against the JDK https://bugs.openjdk.org/browse/JDK-8340727. The JDK internally uses the NSProcessInfo's operationSystemProperty to determine the OS version, which then triggers the log. Well, you can report it as log noise if you like, but it’s definitely not a sign of an actual problem. Later today I will go ahead and report this, through feedback assistant, as a log noise. Thank you for your answers and the detailed technical explanations.

Apple’s frameworks tend to use lazy initialisation, so that fact that you’re seeing this message indicates that someone called upon the user defaults subsystem. Fortunately there’s an easy way to see what that was: Set a breakpoint on _CFPropertyListMissingSemicolon, just like that log message says: % ./Test766100 - '{x=y}' 2024-10-15 08:29:52.210 Test766100[17986:1896989] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug. 2024-10-15 08:29:52.211 Test766100[17986:1896989] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary on line 1. Parsing will be abandoned. Break on _CFPropertyListMissingSemicolon to debug. OS version: 14.7.0 % lldb Test766100 (lldb) target create Test766100 Current executable set to '/Users/quinn/Library/Developer/Xcode/DerivedData/Test766100-eqgrugnuouzcamctylmfxiicxmtz/Build/Products/Debug/Test766100' (arm64). (lldb) br s