I have very similar problem: some users of our app (all on iOS 18.1.1, but device models are different) are not able to register for push notifications. It can be due to bad network, of course, and I tried to simulate this situation (but only had luck on simulator), so here is my experience: If application is offline while calling registerForRemoteNotifications and 3-5 minutes afterwards, appDelegate would never receive didRegisterForRemoteNotificationsWithDeviceToken or didFailToRegisterForRemoteNotificationsWithError. I have a feeling that that may be the case for affected users. What would be best approach in this case? On simulator, I tried to call registerForRemoteNotifications but that never trigger didRegisterForRemoteNotificationsWithDeviceToken. However, on device registerForRemoteNotifications always matches didRegisterForRemoteNotificationsWithDeviceToken

Same

PDF contains "angular gradient" element from Figma

macOS Monterey, Xcode 13.4.1 iOS simulator: iPhone XS Max 14.5 real device: iPhone XS Max 14.6

Bitcode is indeed enabled for our app since it was strongly encouraged before. (We are going to get rid of it ASAP, but we still have to figure out what's going wrong) So in our case, archived app is not the same as the one executed on devices of customers.

Thanks, but that was quite obvious. Problem is that none of those issues can be reproduced. Crashes are specific to App Store builds and are happening in random places. For example, in one of the crashes [AVCapturePhotoSettings dealloc] is called, and I never create AVCapturePhotoSettings on application start. There is a place when this object is created, but it's deep inside lifecycle. Can it be that those crashes are related to recompiling of the app by appstore/testflight?