You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CloudKit sends retryAfter with THROTTLED / TRY_AGAIN_LATER. MistKit decodes it in the per-record error schema, but the top-level ErrorResponse doesn't declare it. A request that fails outright as throttled therefore reaches callers without the server's back-off time.
Proposal: add retryAfter to ErrorResponse, expose it on the throttled/try-again CloudKitError cases (for example retryAfter: TimeInterval?), and add a test with a recorded response.
Found while building brightdigit/Mistico (vendored at Packages/MistKit, branch mistico from v1.0.0-beta.6). Tracked in brightdigit/Mistico#106.
Activity