@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()

isSIMInserted is broken and doesn't work with beta 1 and beta 2, you need to use beta 3. And the subscribers should be obtained via CTSubscriberInfo.subscribers() .

I filed a feature suggestion years ago, FB12745207. It remains open to this day. I know that similar feature requests have been filed by large well know companies.

No. Carrier apps can use a private api to detect the phone number, but there's no public api available to do that.

You can't prevent the app from moving to the background.

I've been using RN in a large app for a few years. The larger and more complex the project becomes, and especially the more and more things that get implicitly and explicitly pulled in by RN then the more and more and more unstable Xcode becomes in being able to compile it, and then run it. I can't speculate from what you've posted what the issue is, and am not familiar with that framework being used, but from experience if you clean everything (I mean everything, including deleting the node_modules folder and the pods folder and everything in Xcode) and restart the Mac then there's a 95% chance issues go away.

Yes it does, I forgot to select the All tab, its set to the Basic Tab by default

Well that's impossible. An iPhone app doesn't have the capability to detect an incoming call never mind listen to the content. Apple themselves of course would have the ability to do this, but not anybody else unless they have a server integrated with the telephony system. An Android app could with certain permissions, but that's not for this forum.

I have the same problem. Also iOS 17's CTSubscriber.simInserted() has stopped working in iOS 18. So forwards compatibility has been broken (apps released using CTSubscriber.simInserted() no longer work).