Dhiogo Brustolin

Hello @Kemberz. Your problem is not related to Sentry.

Thanks @iDevPro for reaching out. We will discuss how to fix this warning.

Push notifications in iOS are handled through the UNUserNotificationCenter framework and its delegate methods. In order for the app detect a push notification the App delegate needs to implement UNUserNotificationCenter,...

We need to investigate [getDeliveredNotifications:](https://developer.apple.com/documentation/usernotifications/unusernotificationcenter/1649520-getdeliverednotifications)

Using [getDeliveredNotifications:](https://developer.apple.com/documentation/usernotifications/unusernotificationcenter/1649520-getdeliverednotifications) does not looks like a good solution, because the most common path regarding notifications is to call `removeAllDeliveredNotifications` after the app open so the notifications don't hang forever...

The solution to this will be using Swizzling. We need to have tests to make sure we're not preventing the app to get the notification. We need to have this...

Technically, yes, but this should not happen. Once it goes into the background for more than 30 seconds, we should not consider it the same session.

Instead of ignoring the app hang we could suspend the first 70 threads to capture the stack trace, and adding the other threads without stacktrace the same way a normal...

I believe this is an edge case that don't worth doing option B.

> Turns out you cannot use Sentry and Sentry-Dynamic at the same time You're right, those are the same libraries, but different linking types (static and dynamic). We will revisit...