macOS 13.2 App scenarios to Handle NSUserDefaults Synchronization Across Multiple Instances
I've looked through the documentation and I'm still confused about I'm developing a macOS 13.2 application that relies on NSUserDefaults for storing user preferences. Recently, I've noticed that changes made in one instance of the app are not reflected in another instance. I've ensured that I'm using `NSUserDefaults.standardUserDefaults` to access the defaults. However, when I modify a value in one instance and check it in another, the value remains unchanged. Here's a snippet of the code I'm using to update the value: ```swift let userDefaults = UserDefaults.standard userDefaults.set("NewValue", forKey: "myKey") userDefaults.synchronize() // This is called to ensure immediate write ``` Despite calling `synchronize()`, I still observe that when I launch a second instance of the application, it doesn't read the updated value. I have tried using `userDefaults.object(forKey: "myKey")` to retrieve the value, but it consistently returns the old value. I've also checked if my app is running in the sandboxed environment, and it's not. I am curious if there are any particular considerations or best practices for ensuring NSUserDefaults is synchronized across multiple app instances in macOS. Can anyone guide to understand what could be causing this scenario and how to resolve it? This is part of a larger CLI tool I'm building.