iOS教程中plist读写异常求助：存储无报错但读取不到数据

Hey there! Let's break down why your fetchNotes() is returning an empty/nil result even though save() doesn't throw errors—this is a super common pitfall when starting out with iOS data persistence, so you're not alone. Here are the most likely culprits to check:

1. You're writing to the wrong file path (or reading from a different one) #

A huge number of beginners accidentally try writing to the app's main bundle, which is read-only. You need to save your plist to the app's Documents directory instead. And crucially, make sure both your save() and fetchNotes() methods use the exact same URL.

Here's how to correctly get the Documents directory path:

private func getDocumentsDirectory() -> URL {
    let paths = FileManager.default.urls(for: .documentDirectory, in: .userDomainMask)
    return paths[0]
}

// Use this URL for both save and fetch
private let plistURL = getDocumentsDirectory().appendingPathComponent("Reflections.plist")

Double-check that you're not using Bundle.main.url(forResource:...) for saving—that will silently fail because you can't write to the bundle.

2. Your Reflection model isn't properly serializable #

Custom objects can't be written to a plist out of the box. You need to make your Reflection class conform to either Codable (the modern, simpler option) or NSCoding.

If using Codable: #

Make sure your model implements Codable (if all properties are basic types like String, Date, Int, this is automatic):

class Reflection: Codable {
    var title: String
    var content: String
    var date: Date
    
    init(title: String, content: String, date: Date) {
        self.title = title
        self.content = content
        self.date = date
    }
}

Then update your save/fetch logic to use PropertyListEncoder and PropertyListDecoder:

// Save method
func save(reflections: [Reflection]) {
    let encoder = PropertyListEncoder()
    do {
        let data = try encoder.encode(reflections)
        try data.write(to: plistURL)
    } catch {
        print("Save failed: \(error.localizedDescription)")
    }
}

// Fetch method
func fetchNotes() -> [Reflection] {
    guard FileManager.default.fileExists(atPath: plistURL.path) else {
        return [] // Initialize empty array if file doesn't exist yet
    }
    
    let decoder = PropertyListDecoder()
    do {
        let data = try Data(contentsOf: plistURL)
        return try decoder.decode([Reflection].self, from: data)
    } catch {
        print("Fetch failed: \(error.localizedDescription)")
        return []
    }
}

If using NSCoding (older approach): #

You'll need to implement init?(coder:) and encode(with:):

class Reflection: NSObject, NSCoding {
    var title: String
    var content: String
    var date: Date
    
    init(title: String, content: String, date: Date) {
        self.title = title
        self.content = content
        self.date = date
    }
    
    required init?(coder: NSCoder) {
        title = coder.decodeObject(forKey: "title") as? String ?? ""
        content = coder.decodeObject(forKey: "content") as? String ?? ""
        date = coder.decodeObject(forKey: "date") as? Date ?? Date()
    }
    
    func encode(with coder: NSCoder) {
        coder.encode(title, forKey: "title")
        coder.encode(content, forKey: "content")
        coder.encode(date, forKey: "date")
    }
}

And use NSKeyedArchiver/NSKeyedUnarchiver for saving/fetching (note: for iOS 12+, use the modern archivedData(withRootObject:requiringSecureCoding:) method).

3. You're not handling the "first run" scenario #

When your app launches for the first time, the plist file doesn't exist in the Documents directory yet. If your fetchNotes() doesn't account for this, it'll return nil or an empty result (hence your "No Notes" message).

Add a check for file existence in your fetch method, like the example above—return an empty array instead of letting the read fail silently.

4. You're ignoring errors in your save method #

You mentioned save() doesn't throw errors, but are you actually catching them? If you're using try? instead of a proper do-catch block, errors will be suppressed, so you won't know if the save failed for reasons like invalid data or file permissions.

Always wrap your save logic in a do-catch and print the error—this will give you critical clues if something's wrong.

5. Data type mismatch between save and fetch #

Double-check that the type you're writing to the plist matches what you're trying to read. For example, if you save an array of Reflection objects, don't try to decode it as an array of [String: Any] dictionaries later. The encoder and decoder must work with the exact same type.

内容的提问来源于stack exchange，提问作者A Tyshka