I second _nox, am testing against IOS 18, but this seems to have broken for my app a few weeks ago. I had hoped the big upgrade would have fixed this. I have verified that the token I have in my db matches what my app gets in didRegisterForRemoteNotificationsWithDeviceToken at startup, and whether I build my app in production or development I get the same token, which seems peculiar. If I build and push from apple web site console to production I see "The specified device token is invalid. Verify that the request contains a valid token and that the token matches the environment." with APS Env set to production, but if I build to development and send to development, from their web console thingy, I get "discarded as device was offline" from my server sending the production works always giving me sendToToken com.eatthepath.pushy.apns.util.concurrent.PushNotificationFuture@5770671b[Not completed, 1 dependents] but sending with the development cert I get io.netty.channel.ConnectTimeoutException: connection timed out: api.push.apple.com/[2620:149:149:1029:0:0:0:1f]:443 This has been working for a while, albeit I've just been using production for testing since the sandbox hasn't worked in a long time. However, this system seems to be down or my particular app is being blocked. I've always been an android developer, and am trying to work cross platform these days. It seems to me that a working push notifications system is kind of a minimum requirement. This is costing me time and money as I'm not sitting around collecting a big Apple Pay check nor getting stock options.