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

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?

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)."

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}}}

Hello, I filed FB14505986

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" ] ],

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 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.

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

Thank you

I changed the urls used from http://MacBook-Pro.local:8080 to the Mac's ip address:8080 and now get this error instead: configure failed Error Domain=com.apple.CipherML Code=1100 "Unable to query status due to errors: failed to fetch token" UserInfo={NSLocalizedDescription=Unable to query status due to errors: failed to fetch token, NSUnderlyingError=0x9fc845ef0 {Error Domain=CipherML.AuthenticationError Code=3 "failed to fetch token" UserInfo={NSLocalizedDescription=failed to fetch token}}} Presumably this has something to do with service-config.json contents: { "issuerRequestUri": "http://192.168.1.4:8080", "users": [ { "tier1": {} }, [ "AAAA" ], { "tier2": {} }, [ "BBBB", "CCCC" ] ], The instructions for this say "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."

Which parts of the Apple documentation on submitting apps is lacking or unclear?

I get the exact same thing, its been present from Beta1 to Beta4. It crashes all the time, therefore I am unable to build our app using Xcode 16. I filed a radar when beta 1 came out, but that's gone ignored.

This is a question entirely to do with React Native and nothing to do with iOS/Swift etc. and therefore is not an appropriate forum. Stackoverflow would be better. You could try adding the following to the Bundle React Native build phase to see if that works: if [ -d "/opt/homebrew/bin" ] && [ -x "/opt/homebrew/bin" ]; then export PATH="$PATH:/opt/homebrew/bin" fi

Yes there is documentation of this API, but as this feature is intended for cellular carriers the documentation is not publicly available. If it doesn't work then its for one of 3 reasons: The app doesn't have the sim-inserted entitlement The MCC/MNC pairs doesn't match that of the sim(s) present on the device The app is itself creating a CTSubscriber as in the above code rather than obtaining it from CTSubscriberInfo.subscribers()