Presumably the two apps/companies know something about each other - otherwise what could be the possible point in trying to share a piece of data. So could app A enable deep linking via a url and then app B invokes that url with the token appended.

You can't do this on iOS - you can't trigger your app to run at a specific time or periodically. Your alternatives are to write a server, and you server co-ordinate things and send a push to the app. Alternatively, live activities might be a good fit for what you want to do.

No it isn't

@Kevin Elliot "Why? All other issues aside, I'd expect this to be a fairly rare edge case. Is there a reason why this is particular issue for your users/use case?" As echu says "It's a problem because people add known spammers to their contacts" Exactly. I'm a developer, but also an iPhone user and as a user I do this myself.

I discovered that logging doesn't appear at the point when the extension is enabled and the extension is specifying a set of sub actions. If no sub actions are specified then logging reappears. Its exactly the same as reported in this ticket here, so probably connected to this ticket: https://developer.apple.com/forums/thread/764561

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.