smb big sur

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

This problem for me (I use iOS 18 on iPhone) is a big problem because my app cannot do settings !!! Please say us something about that feature !!!

Unfortunately I've a lot of settings in root.plist (and other) and since iOS 18 that doesn't work : we see only few Apple prefs in my app Settings. This is a big problem for me ...

The example app from this link is also not working on my iPad: https://developer.apple.com/documentation/swiftui/building-a-document-based-app-using-swiftdata I was a big fan, but I’ve decided to move away from SwiftData. Instead, I’ll switch my data model from @Model to @Observable and Codable, and figure out a way to store it as JSON.

@DTS Engineer Having the same problem here: building an app on Xcode 16.0 on macOS Sonoma 14.7 results in an application that crashes on macOS Big Sur Intel machine with the same crash as mentioned above. Building with Xcode 15.4 does not have this issue. However, we cannot build this branch on Xcode 15.x anymore due to code changes for Xcode 16 compatibility. Is there a workaround? We're now stuck in an unreleasable state!

I can upload builds if you need them, but it would appear to be pretty obvious that there is a big problem with XCode16. This same project was successfully built and deployed with XCode 15 before I upgrade my Mac and XCode last night