smb big sur

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

Again @Kevin, I'd like to stress how much I appreciate your feedback here. If we disagree on something, it's not a reason to turn this into a heated discussion. ABOUT DOCUMENTATION I really apologize, but I have to touch the subject of documentation once again, I promise it will be for the last time… It may very well be that I didn't get it quite right because of not being a native English speaker. Or maybe even more so because I really liked the existence of old CMPlugin (macOS 10.6 Leopard or older) and hated when it was discontinued (but I admit, it was discontinued for good reasons) that I perhaps immediately saw Finder Sync as a sort of its revival. Those things might have influenced a lot my ideas of potential usage for Finder Sync. But I still maintain that the documentation wasn't clear about its ONLY INTENDED usage (remote content/data syncing). Yes, the very first sentence of the original document says: In OS X, the Finder Sync extension point lets you cleanly and safely modify the Finder’s user int

I have a big revision of the LNP FAQ in the works, but it’s not done yet )-: In the meantime, I can confirm that there’s no mechanism to authorise local network access through a configuration profile. [quote='766178021, this_username_did_not_exist, /thread/766178, /profile/this_username_did_not_exist'] It seems a bit strange considering that this feature has been available on iOS for at least 3 years. [/quote] Right. That suggests that this isn’t an omission, but a deliberate design choice. If this feature is critical to your organisation, I encourage you to file an enhancement request that explains why it needs to to be able to force the user’s privacy settings. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Let’s tackle you big picture question first and then come back to the details: [quote='766021021, konradedgar, /thread/766021, /profile/konradedgar'] can I deploy the App on the App Store and use NSAppleScript as shown above? [/quote] Probably not. I don’t work for App Review, and they’re the only folks who can give you definitive answers about what is or isn’t allowed on the store. However: When you use NSAppleScript, the Apple events originate in your process. For a sandboxed process to send arbitrary Apple events, it must be signed with the com.apple.security.temporary-exception.apple-events temporary exception entitlement. My experience is that App Review only approves the use of such entitlement is exceptional circumstances, for example, to work around a sandbox bug on older systems where the bug is fixed on the latest system. If you want a more definitive answer, you’ll need to talk to App Review directly. [quote='766021021, konradedgar, /thread/766021, /profile/konradedgar'] will I need to sto

[quote='766100021, jaikiran, /thread/766100, /profile/jaikiran'] Should this be reported as an issue through feedback assistant … ? [/quote] No. Well, you can report it as log noise if you like, but it’s definitely not a sign of an actual problem. Foundation was created as part of Apple’s (well, NeXT’s) app development story. For this reason it contains a component, UserDefaults, with some helpful, but non-obvious, behaviour: You can override specific user defaults by passing them on the command line. For example, consider this program: import Foundation func main() { print(UserDefaults.standard.string(forKey: QTest) ?? -) } main() If you run it with no arguments it gets nil back for this default: % ./Test766100 - But you can supply a default as an argument: % ./Test766100 -QTest 'Hello Cruel World!' Hello Cruel World! This mechanism supports all property list types. That’s super useful in some cases. For an example of that, check out this post. This log message is being triggered by the property list parser