I'm also seeing this in my development environment and only on Big Sur (currently version 11.1) It reports being registered: NSApp.isRegisteredForRemoteNotifications: true Connection to APN port seems established: ─$ netstat |grep 5223 tcp4 0 0 macbook-pro-6.la.53515 17.57.146.6.5223 ESTABLISHED But didReceiveRemoteNotification didRegisterForRemoteNotificationsWithDeviceToken didFailToRegisterForRemoteNotificationsWithError are never called. (It's a bit confusing that there are only so few of us reporting this. Wouldn't there be more complaints if it was affecting everyone?)

It still the same on Big Sur 11.3.1. I am just wondering, could it be that we are supposed to switch to something else and not use this any more? And if it's not working in production now - what are we going to tell our customers?

Praise be (to Darwin and Turing and Ada Lovelace and whoever fixed this) Big Sur 11.4 - it works!!