How to fetch the latest identity info after the service is updated?

[hoocbee]

Hi,

I wonder how the client could fetch the updated number identity info after the server updates input.txtpb?

At first, the content of my input.txtpb file was like this:

After executing the ConstructDatabase, PIRProcessDatabase and PIRService commands, I installed my App and turned on the LIVE CALLERID LOOKUP, and successfully displayed "ID1" when the call came in.

Then, I changed the name of the input.txtpb file from “ID1” to "ID2".
However, after I re-executed the ConstructDatabase, PIRProcessDatabase and PIRService commands:

• After "ID1" expires (5 minutes as configured above), when the same call comes in, the name I fetch is empty.
  

• Only after I execute the LiveCallerIDLookupManager.shared.reset and LiveCallerIDLookupManager.shared.refreshPIRParameters methods in the app can I fetch the "ID2" normally

I wonder what is the correct way to do this? Or is there a bug here? From the API comments of LiveCallerIDLookupManager, it seems that is not necessary to execute the refreshPIRParameters method when just modify the name?

[hoocbee]

In addition, if I only execute the ConstructDatabase and PIRProcessDatabase commands without executing the PIRService command after change the name of input.txtpb from "ID1" to "ID2" :

• After "ID1" expires, when the same call comes in, the name I fetch is still "ID1".

[karulont]

What happens, is that by restarting the server, you also invalidated a few other things: cached access tokens, evaluation key stored on server.

So that is the reason why you needed to use the refreshPIRParameters.

#22 adds some additional information about it.

[hoocbee]

So, if I modify the content of the input.txtpb file, do I have to restart the service?
As I added in the comment above, it seems that if the service is not restarted, the client will still fetch the old name ("ID1") . Is this as expected?

[karulont]

This is expected for the example service. It only loads the service-config and the usecases defined there at startup. So following changes to the files fill not affect the service until the service is restarted(which also invalidated a few keys).

[hoocbee]

Got it, thanks!

[minnow54426]

Hi,

I wonder how the client could fetch the updated number identity info after the server updates input.txtpb?

At first, the content of my input.txtpb file was like this:

After executing the ConstructDatabase, PIRProcessDatabase and PIRService commands, I installed my App and turned on the LIVE CALLERID LOOKUP, and successfully displayed "ID1" when the call came in.

Then, I changed the name of the input.txtpb file from “ID1” to "ID2". However, after I re-executed the ConstructDatabase, PIRProcessDatabase and PIRService commands:

• After "ID1" expires (5 minutes as configured above), when the same call comes in, the name I fetch is empty.
  
• Only after I execute the LiveCallerIDLookupManager.shared.reset and LiveCallerIDLookupManager.shared.refreshPIRParameters methods in the app can I fetch the "ID2" normally

I wonder what is the correct way to do this? Or is there a bug here? From the API comments of LiveCallerIDLookupManager, it seems that is not necessary to execute the refreshPIRParameters method when just modify the name?

Hello, now i have run PIRService successfully, you wrote that "i installed my app and turned on the LIVE CALLERID LOOKUP", can you say more details about this? After starting the PIRService, the document only says that we need a LiveCallerIDLookupExtensionContext, however I don't know anything about where to create this context and how to use it.
Thanks very much

[karulont]

Please see the documentation at https://developer.apple.com/documentation/identitylookup/getting-up-to-date-calling-and-blocking-information-for-your-app

[karulont]

Also wanted to add: that we added a way for the service to reload the configuration without having to restart the service.

#47