Airship iOS SDK crashes in Swift 6 at calculateBackgroundWaitTime

TL;DR

Update the Airship iOS SDK to 19.11.1 or later. You changed no app code, the crash is inside the SDK's rate-limiting internals.

Steps

1. After migrating your app from Swift 5 to Swift 6, crashes appear in the Airship SDK

at Workers.calculateBackgroundWaitTime(maxTime:). You changed no app code, the crash is inside the SDK's rate-limiting internals. It is a Swift 6 strict concurrency issue, not a bug in your integration.

2. Update the Airship iOS SDK to 19.11.1 or later. Maintainer rlepinski refactored

WorkRateLimiter upstream to remove the crash path.

3. Bump the Airship dependency: 19.11.1 minimum (newer is fine).
4. Rebuild and re-run. The reporter confirmed the crash is gone on 19.11.1.
5. • The crash stack points into the SDK (Workers.calculateBackgroundWaitTime),

   not your call sites.

• It appears only after the Swift 6 migration.
• No app-side changes are needed; the SDK update alone resolves it.

When to use

You are seeing this: After migrating your app from Swift 5 to Swift 6, crashes appear in the Airship SDK at Workers.calculateBackgroundWaitTime(maxTime:). Use this skill when you run into "Airship iOS SDK crashes in Swift 6 at calculateBackgroundWaitTime".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 19.11.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

A user reported that after migrating apps from Swift 5 to Swift 6, crashes appeared in the Airship SDK at Workers.calculateBackgroundWaitTime, a Swift 6 concurrency crash in the SDK rate-limiting internals rather than app code. The verified resolution from maintainer rlepinski: update the Airship iOS SDK to 19.11.1 or later, which refactors WorkRateLimiter to remove the crash path; the reporter confirmed the crash is gone. Thread: https://vectle.com/threads/thr_ys5Q6Njwlv-nJepG-U1fWA