smb big sur

Hmmm, that’s interesting. With System Configuration framework, the keys that are listed in are generally considered API. Both of the keys you’re using, SMB and Workgroup, are listed present [1], namely kSCEntNetSMB and kSCPropNetSMBWorkgroup, so I would expect this technique to continue to work. Given that, I encourage you to file a bug about them being missing. Please post your bug number, just for the record. The other place to get this info is from Open Directory. It’s been a long time since I’ve looked at this, so I’m a little fuzzy on the details. Can you find the info you need via dscl? If so, post the details and I can explain how to get the same info with the OD API. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Much to my surprise!

Say, they picked 10 files from gdrive and another 5 from local storage. If I encounter some errors on the files from gdrive I want to stop working on all 10 of them but to do that I need to be able to determine that that are on this particular volume. You seem to be making the assumption that e.g. Google Drive will be a separate volume compared to local storage, but for the record this is not how these things generally work; files from this kind of “file providers” will still reside in local storage, and the File Provider framework is the one which synchronizes them with their remote storage behind the scenes. (Your concern of course still applies for external drives, SMB shares and the like.)

I agree with @dev-ios this is a big issue. I hope apple will provide some solution soon.

UPDATED: I forgot to mention that I am not running a beta, this is the gold release that has this issue (But I feel like its a beta) and I only singed into the dev side to see if a beta might have the fix for this. I agree, it should be raised as a bug. But I also think this should have never been a bug with a new phone pro model that always focuses on the camera. I’ve had his issue also, along with photos not displaying correctly when I look at them from the camera app, videos recording without now sound. And in a time I needed it to work and document damage from the storm for insurance reason. At the price of a iPhone 16 pro max this was a big failure.

I agree, it should be raised as a bug. But I also think this should have never been a bug with a new phone pro model that always focuses on the camera. I’ve had his issue also, along with photos not displaying correctly when I look at them from the camera app, videos recording without now sound. And in a time I needed it to work and document damage from the storm for insurance reason. At the price of a iPhone 16 pro max this was a big failure.

I'm observing all sorts of race conditions occurring in various VNOPs my custom filesystem implements. I'm inclined to attribute this to my implementation not following the locking rules expected by the system of a 3rd party filesystem as well as it should. ... Thus my question, what are the locking rules for VFS and VNOP operations? The term rules here is very misleading. On it's own, the VFS system doesn't necessarily require any locks at all. When you look at something like this: I've looked at how locking is done in Apple's own implementation of Samba and NFS clients. The Samba client uses read/write locks to protect its node from data races. While the NFS client uses mutex locks for the same purpose. While some of those looks are about the vfs implemenation itself (VNOP_LOOKUP is one example), most of the locking are about ensuring the the file system itself behave in a sane matter. As the simplest example, it's hard to see how a basic operation like file moving could be implemented unl

[quote='806393022, karl-police, /thread/764956?answerId=806393022#806393022, /profile/karl-police'] If I click on Individual it just tells me that I can't enroll at the time. [/quote] That’s weird. We can’t debug issues like this here on DevForums because it requires sharing of personal info. If, after us talking here, you decide you want to pay to join the Apple Developer Program, I recommend that you open a formal support case via Apple > Developer > Contact Us. However, before we do that I’d like to clarify the big picture. You wrote: [quote='764956021, karl-police, /thread/764956, /profile/karl-police'] But I want to do it in an official way. [/quote] There is an official way to deploy apps to an iPhone without paying to join the Apple Developer Program. However, it requires you to use Xcode (or Swift Playgrounds). These support the concept of free provisioning, otherwise known as a Personal Team. You log in with any Apple ID and it lets you run your app on your own device. IMPORTANT The Pe

Does anyone know from a hardware or software point of view, what kind of usb keyboard operation will cause the macos system to wake up? Starting up with a few questions: What do you mean by wake up kernel's concept of sleep is very different than user spaces, so there's a big difference between the screen woke up again and the USB bus powered up again. What API(s) are you actually communicating through? One of the user space user clients (which one?) or are the commands coming from a a DEXT or IOKit driver? Are there any other components involved here, particularly 3rd party drivers? Or can someone give us guidance, how to debug and solve the usb keyboard caused by the wake up system problem on Mac OS system? Conceptually, you can broadly think of sleep/wake as being managed at three different levels: User space apps can directly defer/prevent sleep, either directly using APIs like the ones in QA1340 or indirectly because an API the called did the same sort of thing. One thing to note here is that th

Hi @snemiot, You wrote: If I understand correctly, after the migration if a user performs a sign-in with Apple, they will send an access_token that differs from the one they were sending when the app was assigned to the old team. In case I didn't take any action that means that my system would think this was a new user given the access_token has never been seen before, and therefore it will create a new user. Is that correct? Correct, but the app's migration to a new team (from Team A to Team B) also causes all tokens and identifiers for the user to change due to the new association of the recipient team (Team B). So, along with the access_token, the refresh_token, id_token, user ID (id_token.sub) as well as the private email address would differ from what Team A received, because all of this data is team-scoped. Next, you wrote: [...] Does that make sense? Would it work? I'm not a fan of messing with the login logic (having a look at transfer_ids, looking for matches, and so on), especially because there doe