FileStorage strategy reading co.pointfree.Sharing.FileStorage.stub instead of serialized JSON

[cabeca]

Hello!
I have defined a FileStorage based SharedKey like this:

public extension SharedKey where Self == FileStorageKey<DeveloperToolsSettings>.Default {
  static var developerToolsSettings: Self {
    Self[
      .fileStorage(
        .documentsDirectory.appending(component: "my-file-name.json")
      ),
      default: .default
    ]
  }
}

public struct DeveloperToolsSettings: Codable, Sendable {
    public var overrideService: Bool = false
    public var serviceURL: String = ""
    public var showDateIntervalPickerDebug: Bool = false
... some custom CodingKeys and init(from decoder: Decoder)...
}

Some of our internal users are reporting they receive the following error:

Caught error: dataCorrupted (Swift.DecodingError.Context(codingPath: [], debugDescription: "The given data was not valid JSON.", underlyingError:
Optional (Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected character
'c' around line 1, column 1." UserInfo={NSDebugDescription=Unexpected character
'c' around line 1, column 1., NSJSONSerializationErrorIndex=0})))

And when opening the file, it contains:

co.pointfree.Sharing.FileStorage.stub

Why is this happening, and what am I doing wrong to trigger this problem? I'm using version 2.5.1.

Thanks!

[mbrandonw]

Hi @cabeca, the "stub" file was removed from the library a few months ago (version 2.4). I suppose there is a chance that older clients that have that file around could see the error. But also I believe the error is harmless. It just lets you know of a decoding error and then writes the fresh value to disk. Have you noticed any strange behavior come up besides the warning?

We can look into silencing the error for the specific situation of it being equal to the stub string.

[cabeca]

Ah, that explains why I did not find any mention to that stub in the code. I should have remembered to look at older versions of it. There is no problem with the error, as it is just a purple warning, but 3 colleagues reported it to me and I tried to find why it was happening and I couldn’t explain it. Thank you for your answer!