[Technical Questions] Exception in a random thread after sending local notification

[mmervecerit]

In what area do you have a technical challenge?

Swift

Description

Every time new data is added to HealthKit, I check the fever and lab values. If certain conditions are met, I send a local notification (trigger: nil) and display it as a banner when the app is in the foreground. Everything works fine up until the local notification is received. However, immediately after receiving the notification, Xcode/Simulator throws an exception in a thread. I suspect the issue is related to my design and how I handle actors, but I haven’t been able to pinpoint or resolve it.

Reproduction

If you review this PR, you can check out my code. Take a look at NotificationManager, NeutroFeverGuardStandard, FeverMonitoring, and LabResultsManager.

When you build and run the app (with local firebase running), triggering the notification condition (ANC < 500, fever > 101.4), you'll see the notification appear and then encounter the error. (Apologies, I don’t have a formal test case for this yet.)

Expected behavior

Receiving notifications seamlessly and continuing normal operations without any thread exceptions.

Additional context

No response

Code of Conduct

• I agree to follow this course's Code of Conduct and Contributing Guidelines

[mmervecerit]

@PSchmiedmayer @nriedman

[PSchmiedmayer]

I think the issue might be related to your delegate here: https://github.com/CS342/2025-NeutroFeverGuard/pull/30/files#diff-67157db90c025c91e9b6504b9d0eda7bf9848c7fae501328262a25c255305464R12.

You will need to create a Spezi Module that conforms to NotificationHandler and add that module to your Spezi configuration. ENGAGE-HF has some good example how that was implanted there and @nriedman can add some more context to that: https://github.com/StanfordBDHG/ENGAGE-HF-iOS/blob/main/ENGAGEHF/Managers/NotificationManager/NotificationManager.swift#L25