dsym file

@rpatrick00 , can you please use Feedback Assistant to file a bug report? Please include the instructions needed to reproduce the issue.

Thanks for the post, I think your understanding is great and this is very interesting how you use the API and how it behaves. Your observations touch on some subtle behaviors and design philosophies around file resource handling with (and related APIs) in the frameworks that I have been reading the documentation looking for those. However, most of the time I find it better to create a test project to see how it works. I am not an expert on that field, so we should involved someone from that team as it seems these caches are generally managed by the system to balance performance and resource usage, and not strictly tied to any particular run loop like the main or a background thread's run loop? I need to write some code as maybe creating instances or fetching their resource values on background threads is indeed recommended for performance reasons, especially for potentially blocking I/O operations. As you suggested, using with more control over caching might suit your needs if you require finer-grain

SOLVED. I did log a message before each call of decoder.decodeObject(of: key:) That let me find the issue, and replace: self.aVar = decoder.decodeObject(of: NSArray.self, forKey: someKey) as? someClass by self.aVar = decoder.decodeObject(of: [NSArray.self, NSSet.self, NSNumber.self], forKey: someKey) as? someClass Effectively, someClass has properties that have NSSet properties as well as Int. That was my error, but I still think that Xcode should be able to guess this and provide clearer messages or propose autocompletion. Not yet the case in Xcode 16.4 nor 26.2. I'll file a bug report for enhancement.

So I've discovered if you create the NSURL on a background thread you can get stale resource values even on the next churn of the run loop. But whose run loop 'owns' the URL resources? The main thread's run loop ? The run loop of the thread the URL was created on? Or does NSURL do something like this: - (BOOL)getResourceValue:(out id _Nullable * _Nonnull)value forKey:(NSURLResourceKey)key error:(out NSError ** _Nullable)error API_AVAILABLE(macos(10.6), ios(4.0), watchos(2.0), tvos(9.0)); { // do whatever to get the resource value //-- // schedule delete from cache. [NSObject cancelPreviousPerformRequestsWithTarget:self selector:@selector(clearResourceValueForKey:) object:key]; [self performSelector:@selector(clearResourceValueForKey:) withObject:key afterDelay:0.0]; } I don't see how you can tie cached resource value state to a run loop - it doesn't make any sense to me, especially since the documentation advises doing file operations on a background thread/queue because hitting the disk can be slow.

I figured it out. It seems that when all English strings are provided via NSLocalizedString's value argument, en.lproj is not created. In fact, when mixing localized strings with and without default values, only those that have no default value are included in the final app's en.lproj/Localizable.strings. Still, when running the app, the default value is correctly presented, so I guess since it's not in the strings file it is hard-coded in the executable. Maybe I'm not supposed to use the value argument this way? Should I instead cut all the default values and insert them manually in the string catalog? I was already considering to move all English values for my other projects from the string catalog to the source code so that I directly know what a localized string's contents are, but I'm happy now I didn't do that yet. I created FB21733395.

Thanks for responding. I haven't yet been able to reproduce the issue in a small test project so either they made changes in a macOS update or there is some timing issue and/or way the NSURL is initialized in my real project teases the issue out. But I promise I got stale value for nonexistent NSURLIsHiddenKey until I started explicitly dumping it. In my real project the URL comes for -fileURLWithPath: (and initially created on a background thread). My real project is large and complex so when I have more time I'll have to see if I can isolate the issue in a small sample. Due the request by iOS and the server cache the user may see some discrepancies or additional nuances in how and caching behave, particularly regarding stale values. I'm on macOS. Explicit cache management is recommended, especially when dealing with URLs that may have changed state (e.g., deleted or modified), to ensure your application behaves predictably across different environments and runtime sessions. Also CFURL is documented to have

Thanks for the help on this! Xcode Version 26.2 (17C52), issue seen on iPhone 17, iOS 26.2 simulator. presentedCount was added to highlight the issue, but main concern is that the alert automatically dismisses the first time it is shown (it's hard to tell in the video, so presentedCount was added to make it more visually apparent). Changing the ViewWithAlert properties to Binding doesn't seem to fix the alert dismissal issue. Sample Xcode project: https://drive.google.com/file/d/10S5_xdl_RZeUVSlqfCrgzIGeBFjLjRyb/view?usp=sharing

The challenge we are facing is that certain functionality does not behave correctly when the app resumes the next day without a normal cold start. The primary issue is with the SLM (Sound Level Meter) framework, which relies on audio sessions. In these resumed states, the audio session is not always reinitialized cleanly, causing our calibration process to fail and leading to the core issue we observed. If you haven't already, this sounds like something worth filing a bug about. Have you, and if so, what's the bug number? More recently, we encountered a case where we did not even receive the applicationDidEnterBackground callback. We extended the same force-exit handling to cover this scenario as well. Do you have any more information/context about this case? There are cases where apps aren't formally put into the background (for example, I believe swiping control center down will trigger applicationWillResignActive but NOT applicationDidEnterBackground), but all of these cases should also mean that

Thank you for filing FB21555029. At this time it remains open and under investigation. Please continue testing your software in new system software updates and beta releases as they become available. And please update the status of your bug whenever you do a new test. Please see https://developer.apple.com/download/ for the most recent beta releases.

I recommend filing feedback reports about any of the reasons you have for requiring your own compiled version of the WebKit framework in your app. This is useful information for our engineering teams and information we want to know about. Bug Reporting: How and Why? has tips on creating your bug report. If you intend to use an alternative web browsing engine in your app(s) and you intend to distribute your app through the App Store, please be aware of App Store Guideline 2.5.6 (that you can find on this page). Before copying any Apple built and owned frameworks from a system software installation into your projects please contact Apple Legal (https://www.apple.com/legal/) and obtain a license allowing you to do so.

Our app attempts to install a PDF workflow in ~/Library/PDF Services, but on a clean install of newer macOS versions, that directory no longer exists. Please file a bug on this and then post the bug number back here. It won't change anything about your immediate situation[1], but the nature of the sandbox environment means that we should probably be more aware of the broader consequences this kind of directory removal can have. Attempting to create the folder requires prompting for user permission to access the ~/Library directory and then prompting the user to access the newly created ~/Library/PDF Services directory. This is annoying and awkward. ... We would like to create both directories in one step. So, in terms of direct creation, I can see a few options that should work. If you present a save panel that targets ~/Library/PDF Services, then you should be able to directly create the folder in one pass. That flow is a little weird/awkward since you'll need to force the user to approve that exact