[Bug]: No value associated with key exp

[juliettebee]

Summary

Getting user's timeline returns an error

Reproduction Steps

Sign in, then run try await atProto.getTimeline(). This also happens when running try await safeAtproto.getSuggestedFeeds()

Expected Results

An error not to be thrown

Actual Results

The follow errors are thrown:

keyNotFound(CodingKeys(stringValue: "exp", intValue: nil), Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "feeds", intValue: nil), _CodingKey(stringValue: "Index 13", intValue: 13), CodingKeys(stringValue: "creator", intValue: nil), CodingKeys(stringValue: "labels", intValue: nil), _CodingKey(stringValue: "Index 0", intValue: 0)], debugDescription: "No value associated with key CodingKeys(stringValue: \"exp\", intValue: nil) (\"exp\").", underlyingError: nil))
keyNotFound(CodingKeys(stringValue: "exp", intValue: nil), Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "feed", intValue: nil), _CodingKey(stringValue: "Index 3", intValue: 3), CodingKeys(stringValue: "post", intValue: nil), CodingKeys(stringValue: "author", intValue: nil), CodingKeys(stringValue: "labels", intValue: nil), _CodingKey(stringValue: "Index 0", intValue: 0)], debugDescription: "No value associated with key CodingKeys(stringValue: \"exp\", intValue: nil) (\"exp\").", underlyingError: nil))

What operating systems did you experience this bug? (We'll count Docker as an operating system.)

Other

Operating System Version

iOS 18.1 (22B5075a)

ATProtoKit Version

main branch (de8c222)

Additional Context

Thank you so much for your help!

[MasterJ93]

This is something I've been trying to fix for the past little while and it keeps popping up. I'm still looking into it.

[MasterJ93]

Wait a minute... I'm just now realizing that this was made at 7:44 PM yesterday. I think I've updated ATProtoKit by then. Please update the project and see if the issue persists.

Edit: Okay: the branch you're showing is the latest one. Okay, so yes: it's still persisting. Stubborn little bug that is. I'll get to work on it.

[MasterJ93]

I've temporarily disabled the ability to see that specific property. This will be live in the next patch. I'll look into it a bit further, but the path of least resistance right now is to temporarily disable it. It'll be back in a future update.

This issue will remain open until I know it's fixed.

[juliettebee]

Sorry for such a late response! Latest commit at the time (7321b8c) fixes this issue. Thank you so much

[MasterJ93]

Great!

... however, I can't close this issue until I re-enable the property with the confidence that it won't cause any more trouble. I'll be leaving this open until then. I may ask you to see if it comes back once I do, if you don't mind.