@Kevin Elliott In the example Live Caller ID provided by Apple, the database is fixed, and the above question/answer is saying that's not how a real implementation would function. But how could this be possible if the calling number is not exposed to the LCID server? Suppose there exists elsewhere an ever changing/evolving dataset of information about a phone number, the LCIDS would not be able to perform a live lookup because it doesn't know the calling number? Therefore how could the LCIDS use a live, ever changing data set to formulate its response if it doesn't have a fixed dataset like the Apple example server?

No

I've seen it quite often in the past. It appears randomly, persists for a random amount of time, then goes away randomly. I've just had to wait and try again later whenever it occurs.

@Apple Hello, any comment on how the message filter extension behaves with the single ILMessageFilterExtensionNetworkURL specified, but that urls resolves to two VIPs? For example suppose one of those VIPs is temporarily unavailable/down etc.? What does the OS do in such a situation?

Have you used VPN? That's a cause of this happening - the fix if that was the cause in your case is to delete it from the keychain and re-add it, or reboot your Mac.

Looks like the ability for the extension to access/read from a shared group is now supported, so that could open up some possibilities for the app to switch various setting within the extension based upon the subscription status.

The amount of space Xcode uses has been increasing over the years to tremendous levels. In my case I have several different phones, and several different apps and if you build different apps and run on different phones then the amount of things Xcode squirrels all over the place is astonishingly phenomenally vast. I use the DaisyDisk app to help identify what and where Xcode is consuming massive amounts of storage space.

Thank you. If that single url resolves to two VIPs, how does the OS behave?

@Ed Ford Thank you. This .ipa wouldn't be upload able to Testflight presumably? But if it were, and if it used pushes, then it wouldn't be compatible anyway as it would be a developer build and hence configured to use the APNS sandbox rather than the Prod environment?

So I discovered that in order to stop the OS saying developer mode was disabled, I had to go into the iPhone developer settings and switch on Associated Domains Development. Having to do this is an extra step that is not documented anywhere. However unfortunately it doesn't solve my larger issue, which is getting Network URL Unauthorized in the message filter extension when deferring the request to the server.

Delete me

@Rico "you can use developer mode, and directly pull the AASA from their web server." Could you explain this point further please. How does one directly pull an AASA file?

Thank you, however in this answer which I just found https://forums.developer.apple.com/forums/thread/767859 it says "Your main app should have messagefilter associated domains" So contradictory information?

@Scott Hello. Do you know how to enter a character such as this directly into the xcconfig file? UPDATED - found out how to enter unicode characters on a Mac: Go to System Settings/Keyboard, on the lhs click + and add Unicode Hex Input. Then in the Mac's tool bar at the top switch the keyboard to Unicode, then click Option + the unicode code i.e. in my case Option+2002. The key is to switch to the Unicode input keyboard first.

Here's a bit of specific code example, suppose an app extension wants to obtain the value of something in the info.plist which is in the app's bundle (rather than the extension's bundle). Can it be guaranteed that the app's bundle is always accessible/loaded etc. when being accessed from the app extension? private class func getObjectFromInfoPlist(name: String) -> Any? { var bundle = Bundle.main if bundle.bundleURL.pathExtension == "appex" { let url = bundle.bundleURL.deletingLastPathComponent().deletingLastPathComponent() if let otherBundle = Bundle(url: url) { bundle = otherBundle } } return bundle.object(forInfoDictionaryKey: name) }