Isn't this what you need? App Store Connect API / List All File Sizes for a Build Bundle

[quote='818255022, Engineer, /thread/770854?answerId=818255022#818255022'] 4- There will be a special test server made available closer to the date to verify everything will function [/quote] Is there an ETA for that special test server to be ready for test? Would be great that we could have time to properly test before the final rollout.

While we wait an official response, and that test server, I have found this thread on Stackoverflow where it explains how to validate this before Sandbox is updated, to make sure your server has the correct certificate installed. Most likely it will since this is CA certificate dates from 2019 and started being included in distros at least in 2020 (that I could trace). You'll find that certificate in most Linux distros as a symlink inside: /etc/ssl/certs, so if your server uses a Linux image, most likely will be ready: $ file /etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem /etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem: symbolic link to /usr/share/ca-certificates/mozilla/USERTrust_RSA_Certification_Authority.crt With this path, you can run your own test: $ openssl s_client -connect usertrustrsacertificationauthority-ev.comodoca.com:443 -CAfile /usr/share/ca-certificates/mozilla/USERTrust_ECC_Certification_Authority.crt And it will output the correct response ✅: SSL handshake has read 4477 bytes and written 437 bytes Verification: OK But if you run the same test on api.sandbox.push.apple.com:443, you'll get an error ❌: SSL handshake has read 4691 bytes and written 438 bytes Verification error: unable to get local issuer certificate Let's repeat this test when Apple updates api.sandbox.push.apple.com:443.

You know what's interesting in my specific case? I can see the token being delivered when I check the logs in Console.app: default 10:58:17.653847+0000 SpringBoard <APSConnection: 0x600003d653b0> Received token <80ea34a3 55579e65 3486d18b bcffacb0 64427268 c96bf02e 532d4cd7 9e58759d f94b40f8 dd888069 8a24e50b 166b81e1 f684d664 bf8dded1 be9c7ee7 074fb77c 4fada1d5 69c5944c 2c43371b 228b9cb0> forTopic com.example.app.bundleid identifier 5D29AEF5-060A-4CE3-825E-1E51695E851B But the callbacks are not being called in the app: Neither didRegisterForRemoteNotificationsWithDeviceToken or didFailToRegisterForRemoteNotificationsWithError. I'm using a Development Provisioning Profile. This happens both on a real device and a Simulator, both iOS 18.2.