smb big sur

I can announce that this bug has magically disappeared with the latest version of Xcode Version 16.3 (16E140) installed on my Mac I never got any response back from Apple directly whether this was a bug or not and whether this has been solved in whatever shape or form. Completely in the dark and just by retrying over and over again I finally discovered the bug has been fixed. I would really like to understand what is the purpose of the Feedback Assistant other than a big black hole where you submit a bug into without ever getting any valuable feedback. Very disappointed the way Apple's support for developers is working, given the yearly fee you have to pay. Happy, the bug is miraculously solved so I finally can provide an update of my app that works for Mac (designed for iPad) situations again.

Many, many thanks, Nickkk, for your great suggestion! In the meantime I discovered that the misbehavior disappears in macOS 12 Monterey and macOS 11 Big Sur, that I happen to have installed on two other computers. I don’t know about macOS 13 or 14, that I don’t have already installed anymore. In any case, I finally found the — very unexpected — cause of the bug. I applied Nickkk’s idea. It took me quite a while, because the app is very big and I wanted to reduce it in relatively small steps, so as not to miss the cause of the misbehavior. A few times of course I had to come back to a previous reduction, and so on. Finally I found the part of the code that produces the bug. Here is a description of what is involved. • I wanted to observe NSApp’s property “effectiveAppearance” in order to modify the content of certain windows whenever effectiveAppearance changes, • so in my document class’s init method I added the statement [NSApp addObserver:self forKeyPath:@effectiveAppearance optio

Exactly same issue here, Apple is not clear at all, they just say it wasn't possible to complete. Then you need to call to support to understand what is going on. Payment, same think, the collect your credit card, but don't give you feedback, is the process correct? is wrong? Dude, how apple is big doing sume dub thinks like that? I've never seen any company hidden the errors and don't care with the user is facing, you have to figure out by yourself what is the problem

I’m gonna let Kevin answer your main question I can never resist a good file system question. Searching some more online, I found someone mentioning that one has to request this entitlement from DTS. Is this true? Yes, that is correct. However, the criteria for granting this entitlement are very narrow, so it is only granted to backup applications. I'm not sure that this would qualify: I actually want to make a snapshot of a user-selected directory so that my app can sync it to another volume while avoiding that the user makes changes during the sync process that would make the copy inconsistent. Having said that, I'm also not sure you need volume snapshotting for that. Breaking down your options: Would fs_snapshot_create be faster than traversing the chosen directory and creating clones of each nested file with filecopy and the flag COPYFILE_CLONE? So, there are three options here, loosely ordered by performance: Create a snapshot with fs_snapshot_create. Clone the entire directory using clonefile() (see man

[quote='786668021, taisei_hikawa, /thread/786668, /profile/taisei_hikawa'] Is this concern valid? [/quote] Yes. The details vary based on the specific protocol you’re using but, in general, going ‘too wide’ will waste resources and can potentially slow things down. As to what you should do, that depends on a bunch of factors: How large are the images? And how many do you have to upload? What protocol are you using? If it’s HTTP[S], are you using a background session? Are you talking to one specific server? Or do you need to work with a lot of different servers? If it’s one server, what HTTP version does it use? IMPORTANT There’s a big difference between HTTP/1 and HTTP/{2,3} when it comes to parallelism. If you’re still using HTTP/1, you’ll likely get more ‘bang for your buck’ by upgrading the server to HTTP/2 than by tweaking your client. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Indeed. I guess I should be able to recognise our own documentation code )-: Anyway, with that context, I can answer your specific questions: is the function RefreshAppContentsOperation() where to implement code that needs to be run in the background? Yes and no. In this example RefreshAppContentsOperation is meant to be an Operation subclass that implements the app refresh operation. If you want to use this approach, you’d create your own subclass of Operation and then implement the main() method on that. For example: final class RefreshAppContentsOperation: Operation { override func main() { … your code here … } } However, there are other approaches you might adopt. For example, you might start a Task and run Swift async code within that task. Note The term task is overloaded in this context. The Background Tasks framework uses it to refer to the state that’s tracking the work and Swift concurrency uses it to refer to the state of the code that’s actually doing the work. [quote='786186021, marcofusco111, /t

Migrating a large codebase to Swift 6 is not a trivial task. You can expect to encounter a significant number of issues. However, it’s possible to make rapid progress because, in general, these issues falls into big groups. Once you work on the solution for one of the issues in a group you can apply the same solution to all other issues in that group. There are a couple of standard resources that I generally point folks at here: WWDC 2024 Session 10169 Migrate your app to Swift 6 Migrating to Swift 6 Additionally, the Swift team is actively exploring ways to make this process easier. For a general explanation of the plan, see the Improving the approachability of data-race safety vision doc. There are are a bunch of in-flight Swift Evolution proposals that work towards that vision. So, you have a choice here: You can choose to tackle this today. Or you can wait for those changes to land in a production Swift compiler. If you want to tackle this today then I’m happy to help, but I need to see concrete

[quote='840893022, TinyFish, /thread/785083?answerId=840893022#840893022, /profile/TinyFish'] Your crash report is similar to mine, except for the name of the dynamic library. [/quote] Right. That’s just because my app doesn’t use C++ directly. But both the libraries in question are built-in to macOS and thus I see these results as equivalent. [quote='840893022, TinyFish, /thread/785083?answerId=840893022#840893022, /profile/TinyFish'] Is it possible that it is a bug in macOS …? [/quote] macOS is big enough and complicated enough that literally anything is possible. However, the most likely scenario is that the user changed something without understanding the consequences. My immediate suggestion is that you ask them to check the state of the Open Using Rosetta checkbox, per step 9 of my previous post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks Quinn, I'm sure a new and clean empty project runs, but this is a (big) existing project, objective-c, no storyboard but XIBs, that has run fine before 18.4, for years. As the crash happens before my code is even entered I don't even know where to start! Does this Sanitizer message mean anything to you? What is the problem with MemoryMappingLayout? libclang_rt.asan_iossim_dynamic.dylib__sanitizer::MemoryMappingLayout::Next: 0x10f2dae50 <+0>: cmpl $-0x1, 0x8(%rdi)` With the sanitizers switched off in the Run Scheme the app runs fine in the Simulator, but I have a user that experiences an actual crash on device. That crash is different from what I experience: the app crashes on simulator before entering my code, after displaying the splash screen, while the user has an app that does startup, and can be used for a few seconds, but crashes on a certain input. As is, I cannot even establish if these crashes are related. In the App Analytics in AppstoreConnect I see no increase in the number o

Then VNOP_PAGEOUT gets called. I thought that VNOP_PAGEOUT was only called for mmapped files. No that's not correct, that's definitely not correct. The idea behind the UBC (Universal Buffer Cache) is unify the I/O and VM system into a common architecture. In concrete terms, these to cases: Reading the first 16kb of a file. Mapping the first 16kb of the same file. ...should both return a VM page that's actually backed by EXACTLY the same page in the UBC system. Similarly, writing to the first 16kb of that file and modifying a mapped file both have EXACTLY the same result- that is, they both modify the same page in the UBC. But there are no VNOP_MMAP/VNOP_MNOMAP calls being made for the files being extracted. No, you called cluster_write(), which basically means please modify this pages in the UBC. The current VNOP_PAGEOUT implementation ends up calling err_pageout() for files that didn't get tagged as being memory mapped by VNOP_MMAP. I don't think that's going to end very well. Have you looked at what it's ac

We have a problem in a scenario that SIM lock is disabled so after a phone reboots it has the Internet connection but it is still locked. When you call into the VOIP app the app is not being launched as the result (it seems reasonable because it wouldn't be able to access the keychain items etc...) So first off, yes, this can happen. There are a small number of edge cases (one of which is voip) where the system may launch the app prior to first unlock. This behavior has never been documented and can be somewhat inconsistent, however, it's is also VERY old (it comes the original, iOS 4, voip architecture). Because of that, my advice to voip developers has long been: Don't assume/rely on it always happening. As you've noted the behavior is somewhat odd and there are situations where it will not occur. Be prepared for it to happen and handle it as gracefully as you can/choose. Depending on your app architecture, that could mean handling the call completely or simply reporting and then ending the call. One note o