Its not your phone, its iOS 14.5 that is the problem. In addition to getting the call extension status taking a very long time and then failing after app launch, attempting to update the extension does the same. Also try terminating the iPhone Settings app, then launching and going to the Call Blocking & Identification section - your call extension won't be there, it takes 30 seconds before it appears.

@Gualtier Malde  Thank you, what setting is it that affects this? I have Show Previews set to always and can't find any other setting that makes the content of the notification appear

@MobileTen I mean an application extension, such as an action extension, notification content extension, notification service extension etc. I've rephrased the question to hopefully make it more understandable: Is there a way of using Logger/OSLogStore such that logging performed within an extension can later be retrieved by the application? For example suppose an app is logging like this: let logger = Logger(subsystem: "com.mysubsystem.log", category: "app") logger.debug("app stuff") and suppose an extension (such as a notification service extension for example) logs like this: let logger = Logger(subsystem: "com.mysubsystem.log", category: "ext") logger.debug("ext stuff") Then next time the app runs, if it attempts to retrieves the log with code such as: let logStore = try! OSLogStore(scope: .currentProcessIdentifier) let oneHourAgo = logStore.position(date: Date().addingTimeInterval(-3600)) let allEntries = try! logStore.getEntries(at: oneHourAgo) for entry in allEntries { look at the content of the entry Then within the for loop, there's lots and lots of stuff retrieved, including "app stuff", but there is no "ext stuff". Is there anyway the application can retrospectively retrieve logging performed within the extension?

Forgot to mention that replacing MainInterface in the storyboard with UnwantedCommunicationReportingExtension doesn't work either - when run it results in a similar Unknown class error in the console.

Still not there in Xcode beta 6

Download Xcode directly, rather than installing via the App Store. https://developer.apple.com/download/applications/

(Unless you are a Carrier organization) then you're app cannot programmatically obtain the phone number, nor query the sim like that

iOS 16 isn't officially released yet, and Xcode 14 RN only just came out. Try uploading again in a day or a few

Did some more investigation, and the issue is down to the fact that UIScreen.main.bounds is (0.0,0.0,0.0,0.0) if the com.apple.developer.usernotifications.filtering entitlement is present. Without the entitlement is has values for width and height. This was causing an image with 0 dimensions attemting to be added to the contact. So the question is why are the bounds empty if the entitlement is present?

"But in some devices". Not in some devices, in every device - if the app is terminated and you send it a silent push then the app won't receive it. But if the intention is to display a notification to the user, then why are you using a silent push sent to the app rather than a user push???

You need to get your terminology correct in your requirement as its not clear what you are asking. What does schedule local notification mean exactly? A local notification and a push notification are two different things, your talking about local notification and push notification and so its confusing what you want. A local notification is posted by the app, they can be scheduled by the app to be displayed in the future. A push notification is not a local notification, when the app receives a silent push notification it can display a local notification, but the app cannot receive a silent notification if its not running. There are different types of push notification, if you send a non silent notification then it will be displayed to the user (and will look like a local notification) even if the app is not running.

Switch from using a silent push notification to a user push notification, then that will get displayed to the user even if the app is terminated. If the push payload's notification title/subtitle/body can be set by the server then it will just get displayed to the user directly. If the notification title/subtitle/body needs to be changed after the push has been received, then that can be done by using a notification service extension.

Looks like I have to use xcrun, and update the Mac to Ventura. Going to try and update it now and see what happens

Forgot to mention the WWDC22 session mentions a bunch of stuff to go into info.plist, but it doesn't mention BAManifestURL. In general the WWDC materials seem out of date and no use anymore. Is there some accurate up-to-date documentation?

Second what Ptit-Xav says. If you're installing via running the app in Xcode then (unless you are explicitly changing the scheme setting) you are installing a debug build, which is not the same as a release build, and will often lead to different behaviors.