@Apple I can now enable Live Caller ID in Settings and the OS isn't churning out any errors while doing so. However when a call is made to the handset, I see see the OS is doing a lookup to the PIRService, but its timing out: error = Error Domain=com.apple.CipherML Code=400 "Error Domain=com.apple.CipherML Code=401 "Unable to request data by keywords batch: The request timed out." UserInfo={NSLocalizedDescription=Unable to request data by keywords batch: The request timed out., NSUnderlyingError=0x8b4290a80 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSLocalizedDescription=The request timed out., NSErrorFailingURLKey=http://192.168.1.100:8080/.well-known/private-token-issuer-directory}}}: The request timed out." UserInfo={NSLocalizedDescription=Error Domain=com.apple.CipherML Code=401 "Unable to request data by keywords batch: The request timed out." UserInfo={NSLocalizedDescription=Unable to request data by keywords batch: The request timed out., NSUnderlyingError=0x8b4290a80 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSLocalizedDescription=The request timed out., NSErrorFailingURLKey=http://192.168.1.100:8080/.well-known/private-token-issuer-directory}}}: The service-config.json contains: "issuerRequestUri": "http://192.168.1.100:8080/issue", And the extension contains: serviceURL: URL(string: "http://192.168.1.100:8080")!, tokenIssuerURL: URL(string: "http://192.168.1.100:8080")!, Any suggestions what the issue might be?

I keep getting different results, without changing anything. Initially after changing issuerRequestUrl to "http://192.168.1.100:8080/issue" I was able to enable Live Caller Id on the handset, then while making calls I can see PIRService logging activity such as: 024-07-26T10:35:03-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd2 [PIRService] usecase=["com.nothing.CallerID.block"], duration=51183.29405784607ms 2024-07-26T10:35:03-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd6 hb_method=POST hb_uri=/queries [Hummingbird] Request 2024-07-26T10:35:03-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd6 [PIRService] Authenticating request 2024-07-26T10:35:04-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545d76 [PIRService] usecase=["com.nothing.CallerID.identity"], duration=653737.5059127808ms 2024-07-26T10:35:08-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd5 [PIRService] usecase=["com.nothing.CallerID.block"], duration=51340.32905101776ms 2024-07-26T10:35:08-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd7 hb_method=POST hb_uri=/queries [Hummingbird] Request 2024-07-26T10:35:08-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd7 [PIRService] Authenticating request 2024-07-26T10:35:56-0700 info Hummingbird : hb_id=ced7ba3cf0ddf1039830976d93545dd3 [PIRService] usecase=["com.nothing.CallerID.block"], duration=104154.59704399109ms Although call data wasn't actually getting displayed on the call screen. However since then everything keeps timing out or producing a new error: Error setting enabled to 1 for live lookup extension <IdentityLookup.LiveLookupDBExtension: 0x300e5a120> (entity: LiveLookupDBExtension; id: 0xb3f7121c8073bb90 <x-coredata://83D29F3B-ED40-4358-8373-633F259A6CC9/LiveLookupDBExtension/p1>; data: { blockingInfo = "<relationship fault: 0x302896960 'blockingInfo'>"; identifier = "com.nothing.CallerID"; identityInfo = "<relationship fault: 0x302897680 'identityInfo'>"; isAppStoreVendable = 0; isEnabled = 0; isInstalled = 1; priority = 1; shouldRemove = 0; }): Error Domain=com.apple.CipherML Code=1100 "Unable to query status due to errors: server error ({"error":{"message":"No token key found with key id: [33, 132, 101, 35, 168, 214, 114, 89, 42, 149, 166, 64, 68, 231, 87, 86, 9, 199, 206, 114, 53, 73, 202, 165, 60, 130, 43, 158, 239, 8, 247, 248]"}})" UserInfo={NSLocalizedDescription=Unable to query status due to errors: server error ({"error":{"message":"No token key found with key id: [33, 132, 101, 35, 168, 214, 114, 89, 42, 149, 166, 64, 6 Everything seems really unstable and random.

This is very infuriating, one minute there's no errors, then the next there is WITHOUT HAVING CHANGED ANYTHING. There's just no consistency to anything. For example, out of nowhere new errors appearing when the OS performs a lookup when there's a call: block request returned error: Error Domain=com.apple.CipherML Code=400 "Error Domain=com.apple.CipherML Code=401 "Unable to request data by keywords batch: server error ({"error":{"message":"Evaluation key not found"}})" UserInfo={NSLocalizedDescription=Unable to request data by keywords batch: server error ({"error":{"message":"Evaluation key not found"}}), NSUnderlyingError=0xa40374180 {Error Domain=CipherML.CipherMLError Code=5 "server error ({"error":{"message":"Evaluation key not found"}})" UserInfo={NSLocalizedDescription=server error ({"error":{"message":"Evaluation key not found"}})}}}: server error ({"error":{"message":"Evaluation key not found"}})" UserInfo={NSLocalizedDescription=Error Domain=com.apple.CipherML Code=401 "Unable to request data by keywords batch: server error ({"error":{"message":"Evaluation key not found"}})" UserInfo={NSLocalizedDescription=Unable to request data by keywords batch: server error ({"error":{"message":"Evaluation key not found"}}), NSUnderlyingError=0xa40374180 {Error Domain=CipherML.Cip

I was finally able to get things going. The testing documentation says this of the extension "For the userTierToken, please set it to one of the values that you added in the service configuration file in Running the service section. For example BBBB." I tried changing it to AAAA and then it started working even though BBBB is in there too: "users": [ { "tier1": {} }, [ "AAAA" ], { "tier2": {} }, [ "BBBB", "CCCC" ] ],

Hello, I filed FB14505986

Here are a couple of more issue that appear: <private> XPC request complete, status(0) error:Error Domain=CipherML.CipherMLError Code=5 "server error ({"error":{"message":"No token key found with key id: [186, 183, 73, 109, 88, 42, 99, 19, 116, 183, 189, 131, 111, 95, 249, 54, 122, 9, 44, 65, 69, 234, 109, 2, 214, 146, 210, 97, 207, 93, 139, 80]"}})" UserInfo={NSLocalizedDescription=server error ({"error":{"message":"No token key found with key id: [186, 183, 73, 109, 88, 42, 99, 19, 116, 183, 189, 131, 111, 95, 249, 54, 122, 9, 44, 65, 69, 234, 109, 2, 214, 146, 210, 97, 207, 93, 139, 80]"}})} error = Error Domain=com.apple.CipherML Code=400 "Error Domain=com.apple.CipherML Code=401 "Unable to request data by keywords batch: missing configuration" UserInfo={NSLocalizedDescription=Unable to request data by keywords batch: missing configuration, NSUnderlyingError=0xd623415c0 {Error Domain=CipherML.CipherMLError Code=25 "missing configuration" UserInfo={NSLocalizedDescription=missing configuration}}}: missing configuration" UserInfo={NSLocalizedDescription=Error Domain=com.apple.CipherML Code=401 "Unable to request data by keywords batch: missing configuration" UserInfo={NSLocalizedDescription=Unable to request data by keywords batch: missing configuration, NSUnderlyingError=0xd623415c0 {Error Domain=CipherML.CipherMLError Code=25 "missing configuration" UserInfo={NSLocalizedDescription=missing configuration}}}: missing configuration, NSUnderlyingError=0xd623415c0 {Error Domain=CipherML.CipherMLError Code=25 "missing configuration" UserInfo={NSLocalizedDescription=missing configuration}}}

Hi, Submitted a feedback report as FB14539432. FYI the use case is "The use case for this is if a Live Caller ID server has marked a number(s) as being blocked (due to them being indicated as being malicious, spam etc.) but an individual user wishes to ignore that and permit the caller to ring. (The user could do this by adding the call as a contact, but they may not wish to pollute their contacts this way, if adding the number as identified to the Call Extension enabled the call to ring, it would mean the application can override the server's blocking indication on the user's behalf)."

I've not had any issues with share extension in any of the 18 beta versions. "The main target gets deployed fine, only when attempting to deploy the share extension" I don't understand what this means, what do you mean when you say the share extension is deployed separately from its app?

It often fails when trying to install it via the App Store. Download it as a regular download from: https://developer.apple.com/download/all/?q=xcode

@Technology Evangelist Thank you for the reply. Is there some documentation or example on how to achieve using a different user tier to specify a different dataset in relation to the service-config.json of the example server? Just looking at the structure of the service-config.json (and its description of a couple of things) I wasn't able to see what the connection is between the different user tiers and the use cases.

Yes you could if the app's bundle id root matches your account and its signed with your profiles and certificates etc. (then it is no longer their app, but yours), but for the client there are risks, for example: if the app includes payments then those go directly to you and not to the client, they would have to trust you to give them any revenue you have the power to delete the app at any time from the App Store and they are powerless to stop you As a client I would not personally hand over so much power to a developer, no matter how trustworthy they may be.

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?

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?

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

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]