I updated from 16 beta to 16 proper as soon as it was available. (I've also been having my battery issues for a couple of weeks).

My app has an action extension. I have both Xcode 15 and Xcode 16 installed. If I build with Xcode 15 it works, however if I switch to Xcode 16 and build then it no longer works as expected if run on iOS 18 (if built with Xcode 15 and run on iOS 18 it works, if built with Xcode 16 and run on iOS 17 it works. So its the dual combination of Xcode 16/iOS 18 where it doesn't work). If I run the action extension in Xcode there's red output classified as a fault from the com.apple.extensionkit subSystem: -[_EXSinkLoadOperator loadItemForTypeIdentifier:completionHandler:expectedValueClass:options:] nil expectedValueClass allowing {( _EXItemProviderSandboxedResource, NSString, NSMutableData, NSURL, UIImage, NSUUID, NSMutableArray, NSMutableDictionary, NSMutableString, NSDate, NSError, NSArray, NSValue, NSData, NSNumber, NSDictionary, CKShare )} That doesn't get logged when running with Xcode 15

Firebase does some swizzling. Read their documentation and see if setting the FirebaseAppDelegateProxyEnabled flag to false solves your issue.

"Are these crashes being missed by Crashlytics" Crashlytics can only know about a crash if the app runs after a crash has occurred and in addition Crashlytics gets a chance to upload crash reports. If there's a crash that occurs upon app launch, then the app and hence Crashlytics might not get the chance to run long enough in order to upload crash reports before the app terminates due to the current crash. i.e. if its a crash that always or often occurs at app launch, then Crashlytics probably won't have the execution time it needs to upload reports.

@eskimo "If your app extension needs to get the user’s attention, do that by posting a local notification." In my experience (I've tried it with several) most extension cannot post a notification. If the user grants permission for notifications that is granted to the app, not the extension, that means the extension itself has to request user permission, and that itself isn't possible. Am I missing a trick here?

There's no point setting the minimum time to 15 minutes and then sitting watching it and assuming it'll trigger after 15 minutes, or not long after that. It might not be until a few or several hours later, probably during the night in my experience , have you tried waiting that long?

This happens if the number is in contacts, that's something that didn't previously occur prior to iOS 18

Isn't LiveCallerIDLookupManager.shared.openSettings() intended to "offer a option in settings ... to enable live caller id lookup extension."?

Releasing an app without running it on hardware is an invitation for trouble. Have you at least even tried running it in the simulator in release mode rather than debug mode? You don't need a phone to get crash reports, you can get the ones the users have experienced via Xcode Organizer.

You need to put the iPhone into recovery mode and then connect to a Mac and perform a restore. If you google you should find detailed instructions about how to do this with pictures and steps etc.

@bni. Where did this reply from Apple come from?

I first encountered this with beta 1 building an iOS app and filed a ticket at that time. However it's still occurring in Beta 5. I'm starting to become concerned its not going to get fixed by the time Xcode 16 release comes out, meaning I'll be unable to build my app. I get this error %100 of the time: Process: XCBBuildService [19881] Crashed Thread: 13 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: XCBBuildService [19881]

I understand now what your developer is saying. iOS apps are developed using Apple's programming language Swift. There's a new version of Swift available in Xcode 16, Verizon 6. Your developer is saying you need to migrate your app's code to Swift 6 and/or saying that the app cannot continue to use some libraries unless they too are updated by their developers to support Swift 6 as they won't build (or if they are dead and no longer being maintained then to find alternatives). Apple should not be forcing people to migrate to swift 6, and Xcode should continue to build with apps built using an older version of Swift and therefore the fact that does not occur in your case is perhaps a bug in Xcode and might get rectified in the next release. Something else to try as a temporary workaround is to make sure that the Xcode setting Treat Warnings as Errors is set to NO to see if that makes the errors go away. What they are saying about not being able to upload with Xcode 15 next year is true. I don't think your developer is trying to cheat you but Xcode 16 is still in beta status, a big decision on if things need re-writing/replacing should not be being made yet in my opinion until a release version of it has been made. I found this thread about swift 5 and swift 6 warnings situation, the poster asks a valid question that nobody actually answers https://forums.swift.org/t/please-help-me-understand-the-decision-to-add-swift-6-warnings-to-swift-5/73417

There's some issues with Xcode 16 for me where it will %100 time crash attempting to build a large complex project, and that is preventing it being possible to build. However hopefully that will be fixed by the time Xcode moves from beta to release. "I find it difficult to understand why apple would want to make your app obsolete and force you to re-create it because of an update" They would not. But what does your developer mean by "need to rebuild the entire app" and "re-create it". Rebuild it / re-create it how, by doing what exactly? What are they saying is needed to be done to it?

CallKit has different and separate features, are you talking about incorporating a CallKit CallDirectory extension (this won't allow you to gather caller data by the way), or are you talking about adding VoIP functionality to your app?