Like Gualtier Malde replied. The issue you are seeing with silent/background notifications is expected. And it has been going to that "muted" direction from IOS 11 onwards.. (or earlier). https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app?language=objc The system treats background notifications as low priority: you can use them to refresh your app’s content, but the system doesn’t guarantee their delivery. In addition, the system may throttle the delivery of background notifications if the total number becomes excessive. The number of background notifications allowed by the system depends on current conditions, but don’t try to send more than two or three per hour.

Does not seem to work in IOS 14.1, guess we have to wait for 14.2 then.

Same thing. Seems to be Xcode/SDK version related. Random Core Data related crashes starts to occur when App is compiled using Xcode 12.0-12.2 beta. When app is compiled using Xcode 11.5 or older, app doesn't crash anymore. Runs fine also on IOS 14. Using older Xcode 11 is the current workaround. And yeah, there are errors when app is executed with -com.apple.CoreData.ConcurrencyDebug 1 on all XCode versions. But those has been in project for ages. It seems that something has changed on new Xcode/SDK, which makes builds more prone crashing on Core Data coding errors. Either it's not having anymore compile time magic which fixes the coding errors, or something is changed on execution/ dispatching of Core Data operations..