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.

@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?

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

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.

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.

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.

@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?

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.

No

@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?

@Kevin Elliott Thank you for the reply. Does there need to be, or recommended to be, any relationship between the structuring the contents of the shards and the structuring of user tiers? i.e. suppose one user tier is for providing names only, and another user tier is for providing names plus images. Then is it a good idea to (wrt lookup time speed for example) to have shard(s) which contain data without images and separate shard(s) which contain images? Or can the data in the shards and the user tiers all be jumbled up.

usecase name: this is pretty much fixed on device between identity and block. @Technology Evangelist Is this fixed by Apple, or can an implementation extend what a usecase name maps to?

I saw the same thing, but it just worked 5 minutes ago so maybe fixed.

@Engineer The problem with this approach is that it assumes a debug build of code equates to the development push server and a release build equates to the production server, which is not the case. Its actually not the build, as I said in my question that is important and dictates the push server, its the distribution signing that is. You might have a debug build of code that you want to publish to TestFlight; or you might have a body of code that you first test running with Xcode,then without modifying it you want to build and publish to testflight/App Store; or you might want to create an archive, and then distribute that same archive to TestFlight or as a developer distribution .ipa, and so on. Maybe I could look through the Firebase Crashlytics code, they detect when code is debuggable i.e. when the get-task-allow entitlement is set, I expect that would be useful and relevant to obtain in this case as that will vary with the distribution signing.

@ Ed Ford Thank you for this explanation of possible issues with umbrella frameworks. When Technote 2435 says umbrella frameworks aren't supported, does that mean totally, or depending upon if there are scenarios like this? For example if Library1 and Library2 do not have a shared dependency upon Library A, then things will be OK?