App Extension can not connect to local PIR service

[alvin-twofive]

According to this document https://swiftpackageindex.com/apple/pir-service-example/main/documentation/pirservice/onboarding#How-to-test-without-private-relay
I found that it is possible to test the local PIR service without submitting it to Apple.
I tried it but it doesn't seem to work. My App extension can't connect to the local PIR service.

I tried calling refreshPIRParameters(forExtensionWithIdentifier:) to force update your dataset immediately.
And then in the Console.app I see the following error:

requestStatusForClientConfig:options:dispatchQueue:completionHandler: XPC request complete, status(0) error:Error Domain=CipherML.AuthenticationError Code=7 "failed to fetch token key" UserInfo={NSLocalizedDescription=failed to fetch token key}

I can confirm some settings below:

• iOS version is 26
• App Extension was enabled successfully. I checked by LiveCallerIDLookupManager.shared.status(forExtensionWithIdentifier: extensionName)
• App Extension and PIR service are in the same network. My iPhone can resolve the domain name of the host running the PIR service.
• userTierToken of LiveCallerIDLookupExtensionContext is correct. I use BBBB like example
• Dataset is correct with bundle identifier replacement

{
"users": [
{
"tier": "tier1",
"tokens": ["AAAA"]
},
{
"tier": "tier2",
"tokens": ["BBBB", "CCCC"]
}
],
"usecases": [
{
"fileStem": "block",
"shardCount": 1,
"name": "com.myexample.block"
},
{
"fileStem": "identity",
"shardCount": 1,
"name": "com.myexample.identity"
}
]
}

Is there something I'm missing when setting up the local environment for the PIR service?

[karulont]

@alvin-twofive you closed the issue which probably means you got it working.

Please provide a followup message to write what you did, that might help others in a similar position.

[alvin-twofive]

@alvin-twofive you closed the issue which probably means you got it working.

Please provide a followup message to write what you did, that might help others in a similar position.

Hi @karulont
I found that I should call LiveCallerIDLookupManager.shared.refreshExtensionContext(forExtensionWithIdentifier:) for updating connection info again.
I also think you should add this information to the article about common issues.

Or more effiectively, in the side of the Live Caller ID Extension API, we can add one exception handler for this connection issue to automatically refresh the latest LiveCallerIDLookupExtensionContext info.