👀 Views: 98 💬 Answers: 1 📅 Created: 2025-06-13

macos nscoding swift Swift

I've been banging my head against this for hours. I'm working with crashes in my macOS application when trying to encode and decode custom objects using `NSSecureCoding`. Specifically, the app crashes with a `-[__NSArrayI objectAtIndex:]: index 0 beyond bounds for empty NSArray` behavior when I attempt to decode an array of custom objects. Here’s a simplified version of my implementation: ```swift class MyCustomObject: NSObject, NSSecureCoding { static var supportsSecureCoding: Bool = true var name: String var age: Int init(name: String, age: Int) { self.name = name self.age = age } required init?(coder aDecoder: NSCoder) { guard let name = aDecoder.decodeObject(of: NSString.self, forKey: "name") as String?, let age = aDecoder.decodeInteger(forKey: "age") else { return nil } self.name = name self.age = age } func encode(with aCoder: NSCoder) { aCoder.encode(name, forKey: "name") aCoder.encode(age, forKey: "age") } } // Saving array of MyCustomObject let objectsToSave = [MyCustomObject(name: "Alice", age: 30), MyCustomObject(name: "Bob", age: 25)] let data = try? NSKeyedArchiver.archivedData(withRootObject: objectsToSave, requiringSecureCoding: true) // Loading array of MyCustomObject if let data = data { let loadedObjects = try? NSKeyedUnarchiver.unarchiveTopLevelObjectWithData(data) as? [MyCustomObject] print(loadedObjects?.first?.name) } ``` I've double-checked that my custom object properly implements `NSSecureCoding`, and I'm using `NSKeyedArchiver` and `NSKeyedUnarchiver` with `requiringSecureCoding: true`. However, the crash occurs intermittently when the array is empty. I also verified that the objects are being saved correctly. Has anyone encountered this scenario before? Any insights on why I'm getting this crash or how to handle loading empty arrays without crashing would be greatly appreciated. For context: I'm using Swift on Windows. How would you solve this?