Jakob Mikkelsen

I'm also experiencing the same issue. Is there a way to fix this? ```0x104187b50 BaseNotificationBanner.show(placeOnQueue:queuePosition:bannerPosition:) + 380 (BaseNotificationBanner.swift:380) NotificationBannerQueue.addBanner(_:bannerPosition:queuePosition:) + 78 (NotificationBannerQueue.swift:78) BaseNotificationBanner.show(placeOnQueue:queuePosition:bannerPosition:) + 374 (BaseNotificationBanner.swift:374) BaseNotificationBanner.show(queuePosition:bannerPosition:queue:on:) + 337 (BaseNotificationBanner.swift:337)...

Did anyone manage to get the animation of endpoint to work? Then we could use this as progressive which could be interacted with.

I'm experiencing the same behaviour. @ginesdeka, did you manage to solve this issue?

I have made a PR to fix this issue. Until @ruipfcosta have approved it you can use my forked version on my Github.

Thanks for your quick reply 🙂 It have actually only happened on iOS version `13.7.0` and `13.5.1`. Thanks for helping me get to the bottom of this 👍

Yes the stack traces looks all the same. I have the following observers: **iOSSessionHandler.swift** ``` // Observe for a message from the WatchOS GuaranteedMessage.observe { [weak self] (message) in guard...

Hmm yes that could be a possibility. The weird part is that I don't think it was triggered by a watch switching. I just stumbled upon two new crashes with...

https://stackoverflow.com/questions/63614048/xcode-12-sessiondelegate-has-different-definitions-in-different-modules

@KaneCheshire I have made this PR 🙏🏼

The exact same thing is also happening for me!