TipKit crash on launch (iOS 27.2) — swift_unexpectedError with no app frames

We're seeing a crash from a user on iOS 27.2 that we can't reproduce locally. The crash shows swift_unexpectedError on the main thread with no application frames between the concurrency runtime and the crash.

Our app binary hasn't changed since summer 2025 but this user started experiencing the crash for the first time about a week ago.

Thread 0 (crashed):

Thread 0 Crashed (com.apple.main-thread):
0   libswiftCore.dylib            _assertionFailure(_:_:file:line:flags:)
1   libswiftCore.dylib            swift_unexpectedError
2   libswift_Concurrency.dylib    swift::runJobInEstablishedExecutorContext(...)
3   libswift_Concurrency.dylib    swift_job_runImpl(...)
4   libdispatch.dylib             _dispatch_main_queue_drain
5   libdispatch.dylib             _dispatch_main_queue_callback_4CF
6   CoreFoundation                __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
...                               (standard UIApplicationMain run loop)

The crash occurs 0.45 seconds after launch. The only other active thread at the time of the crash is Thread 6, which shows TipKit driving SwiftData/CoreData work:

Thread 6:

Thread 6 name: Dispatch queue: NSManagedObjectContext 0x110f99500
 0   CoreFoundation        CFBasicHashGetPtrIndex
 1   CoreFoundation        CFBasicHashCreate
 2   CoreFoundation        CFDictionaryCreateMutable
 3   CoreData              _PFCMT_SetValue
 4   CoreData              -[NSManagedObjectContext _retainedObjectWithID:optionalHandler:withInlineStorage:]
 5   CoreData              -[NSManagedObjectContext objectWithID:]
 6   SwiftData             (SwiftData + 373080)
 7   SwiftData             (SwiftData + 281172)
 8   SwiftData             (SwiftData + 359244)
 9   SwiftData             (SwiftData + 355724)
10   SwiftData             (SwiftData + 359208)
11   CoreData              thunk for @callee_guaranteed () -> (@out A, @error @owned Error)
12   CoreData              partial apply for thunk for @callee_guaranteed () -> (@out A, @error @owned Error)
13   CoreData              NSManagedObjectContext._rethrowsHelper_performAndWait(...)
14   CoreData              thunk for @callee_guaranteed @Sendable () -> ()
15   CoreData              thunk for @escaping @callee_guaranteed @Sendable () -> ()
16   CoreData              developerSubmittedBlockToNSManagedObjectContextPerform
17   libdispatch.dylib     _dispatch_client_callout
18   libdispatch.dylib     _dispatch_lane_barrier_sync_invoke_and_complete
19   CoreData              -[NSManagedObjectContext performBlockAndWait:]
20   CoreData              NSManagedObjectContext.performAndWait(_:)
21   SwiftData             (SwiftData + 258584)
22   SwiftData             (SwiftData + 257920)
23   SwiftData             (SwiftData + 326480)
24   SwiftData             (SwiftData + 259564)
25   SwiftData             (SwiftData + 56292)
26   SwiftData             (SwiftData + 385736)
27   TipKitCore            (TipKitCore + 202216)
28   TipKitCore            (TipKitCore + 128232)
29   TipKitCore            (TipKitCore + 124104)
30   TipKitCore            (TipKitCore + 130048)
31   TipKitCore            (TipKitCore + 241553)
32   TipKitCore            (TipKitCore + 152365)
33   TipKitCore            (TipKitCore + 134441)
34   TipKitCore            (TipKitCore + 152629)
35   TipKitCore            (TipKitCore + 134233)
36   TipKitCore            (TipKitCore + 134441)
37   TipKitCore            (TipKitCore + 138237)
38   TipKitCore            (TipKitCore + 134233)
39   libswift_Concurrency  completeTask(swift::AsyncContext*, swift::SwiftError*)

All other threads are idle.

Context:

  • We call try? Tips.configure([.displayFrequency(.hourly)]) early in our startup sequence. The try? should swallow any error from configure itself, but I'm not sure if TipKit spawns its own internal async tasks.
  • Our app uses UIKit (not SwiftUI App lifecycle). We do not use SwiftData directly — any SwiftData/CoreData frames come from system frameworks.
  • The binary hasn't changed since summer 2025, so this appears to be an OS-level regression on iOS 27.x.
  • We cannot reproduce locally.

Questions:

  1. Is there a way to get async backtraces in crash reports from the field, or is this only possible under the debugger?
  2. If TipKit spawns an internal Task that throws into a non-throwing context, would that produce exactly this crash pattern — swift_unexpectedError on the main thread with no third-party frames?
  3. Are there known issues with TipKit's internal SwiftData tasks crashing on iOS 27.x?

Any guidance on narrowing this down without a local repro would be appreciated.

Please post a full Apple crash report for this. See Posting a Crash Report for advice on how to do that.

ps If you have a JSON crash report (.ips) that’d be ideal, but a human readable crash report (.crash) is better than nothing.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi @DTS Engineer thanks for the quick reply and the guide on posting crash reports. I've attached an IPS here (I just replaced sensitive information with XYZXYZ).

Please let me know if I can provide anything else.

tipkit crash adf.ips.txt(21 KB)

Thanks for that crash report.

This is going to be tricky to debug. And, yeah, I agree that this is most likely not your fault, but let’s dive in regardless.

The crashing thread backtrace looks like this:

0 libswiftCore.dylib         … _assertionFailure(_:_:file:line:flags:) + 172
1 libswiftCore.dylib         … swift_unexpectedError + 688
2 libswift_Concurrency.dylib … swift::runJobInEstablishedExecutorContext(swift::Job*, swift::SerialExecutorRef, swift::TaskExecutorRef) + 328
3 libswift_Concurrency.dylib … swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) + 156
4 libdispatch.dylib          … _dispatch_main_queue_drain + 512
5 libdispatch.dylib          … _dispatch_main_queue_callback_4CF + 44
6 CoreFoundation             … __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16

Frames 4 and above are standard runloop stuff, where the main thread’s run loop is servicing the main queue. Frames 3 and 2 are the Swift runtime dispatching jobs, presumably jobs associated with the main actor and hence running on the main queue. Frame 1 is this code which, as noted in the doc comment, is called by Swift when a try! fails.

So, what’s triggering that. The most obvious candidate is frame 2. However, I don’t think that’s actually the case. Consider it’s code here. It basically calls a function member (ResumeTask) passing it a data member as a parameter (ResumeContext). I can’t see any way that could end up in swift_unexpectedError.

More likely is that it’s actually called out to the job, which has started running Swift code, which has hit a try!, which has ended up tail calling into swift_unexpectedError. But I don’t see any good way of finding more info about that.

If you could reproduce this locally you could try to see what info gets logged by the assert (frame 0), which might contain a valuable clue. But that’s not an option because you can’t reproduce this.


Are you only seeing one user with this crash? It sounds they can reproduce the crash with some degree of reliability. Is that right? Have you captured multiple crash reports from them? If so, do you always see the same pattern, where there’s another thread deep in SwiftData courtesy of TipKit?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Thanks for investigating, Quinn! To answer your questions:

  1. Yes, only one user has seen this crash so far.
  2. They see it consistently - unfortunately, the app crashes on open :(
  3. We have two crash reports from this person. Now that you mention it, the second crash is actually slightly different - IPS included below. The main thread stacktrace is the same, but the other frame shows "UIKit.inProcessAnimationManager".

second crash adf.ips.txt(18 KB)

One other question: In my research, I saw that some people have seen TipKit crashes if they call Tip#shouldDisplayUpdates before Tips.configure. That shouldn't happen in my code but maybe in some weird timing situation it might. Could that be my issue? Then again, it only affects one user.

Written by interferon in 915925022

I saw that some people have seen TipKit crashes if they call Tip.shouldDisplayUpdates before Tips.configure.

I don’t follow TipKit closely, so I don’t have specific input on this. But I do have a couple of general comments.

First, that second crash makes no mention of TipKit. I mean, the text tip doesn’t appear in the crash report at all. So it’s not at all clear that TipKit is relevant to this.

Second, I have a trick to share for cases like this, where I’ve heard that something crashes and I’m wondering if my crash has a similar cause:

  1. I create a test app that provokes the known problem.
  2. And run it.
  3. I grab its crash report.
  4. And see how it compares to my crash report. If it’s similar, then this line of inquiry is worth pursuing. If it’s completely different, then chances are that it’s something else.

It sounds like you’re in contact with the user having this problem. If so, and they’re willing to help you try to resolve this, then that offers up a bunch of possibilities:

  • You could have them send you a sysdiagnose log and then grovel through the system log to see if you find anything relevant. See Your Friend the System Log for hints and tips about the system log.
  • Going one step beyond, you could add log points to your app’s startup sequence, which then captured in the system log, and then send them a TestFlight build with that logging.

Oh, and I want to come back to one of your earlier points:

Written by interferon in 856563021

Our app binary hasn't changed since summer 2025 but this user started experiencing the crash for the first time about a week ago.

That’s useful to keep in mind, but it could just be coincidence. Imagine that iOS 27.2 has a bug that triggers this crash. By now you’d have a bunch of crash reports from a bunch of users who’ve updated to that release. The fact that you haven’t suggests that there’s something specific about this user’s setup that’s causing the problem. And that means that the OS update might not be involved at all. The user could just have easily changed some state on their device, or in their environment!, that’s the real trigger for this crash. And you can’t ask them whether they did that because folks just don’t remember those details, even when prompted. To quote Dr House, “Everybody lies.” (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

@DTS Engineer

Thanks, Quinn. I now have a second user who's having the same problem (still a tiny, tiny fraction of my userbase). Both of them described the problem in a little more detail to me. As background, in my app, users can record things on the calendar and the app will schedule UNUserNotification's for the next seven days' worth of events to remind them that they're coming up.

It sounds like the problem happens when these two users schedule something within the next seven days and then re-open the app. When they open the app, my startup code refreshes the notifications (since it could've been a while since the last app open). It looks basically like:

UNUserNotificationCenter.current().removeAllPendingNotificationRequests()
UNUserNotificationCenter.current().removeAllDeliveredNotifications()

for (each day in the next seven days that has an item) {
   let request = // ....
   UNUserNotificationCenter.current().add(request)
}

Specifically, one user scheduled something for the current day and then the app crashed every time they opened it. When they tried on the following day (i.e. when there were no notifications to schedule), the app worked fine until they recorded an item for that day. So there does seem to be a strong signal that this code is where the issue arises. One user is running iOS 27.2.1 and the other is running iOS 27.2.

The odd thing is that none of these UNUserNotificationCenter methods (or my own method) are throwing, so I'm not sure where the exception is coming from.

Written by interferon in 916907022

The odd thing is that none of these UNUserNotificationCenter methods (or my own method) are throwing

Indeed. It’s possible that the uncaught throw is being triggered by code within the OS, or by unrelated code that just happens to trigger it at this point.

It sounds like you’re in touch with a user who can reproduce this problem. Do you think you could convince them to run a TestFlight build? If so, I’d start by creating a TestFlight build from the same code as your shipping build to see if still reproduces the problem. Hopefully it will but, if it doesn’t then it’s good to know that immediately, before going further down that path.

Also, do you have a delegate set on UNUserNotificationCenter? If so, it’d be interesting to see if any delegate methods fire as you run this code. If they do, that’d be another thread to pull on.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Quinn,

Thanks again for getting back. I didn't have a chance to get the users set up with a TestFlight build, but we did discover that having them turn notifications for my app off and then immediately back on again resolved the issue. The app no longer crashes, and they can schedule items in the next few days and the notifications work. It hasn't expanded beyond these two users, and their problems are now resolved.

It could be an issue in iOS - not sure. None of my code changed, obviously, but just resetting the notification info fixed the problem. If it happens again, I'll file a feedback report and try to get more information.