bobpf
bobpf
I get the same issue
So I figured out the issue. Application A had a reference to the shared preference before application B wrote the values. When Application A reads the value it did not...
Really sure it’s not a concurrency issue. That being said I wen down the service route instead. Thanks for the update.
Still getting the same error (v3.4). Is this going to be fixed anytime soon?
Usage of NTPv3 protocol has come up on a security review. Can you comment on its usage and the possibility of getting v4 implemented as the primary protocol or as...
Switching the protocol to us NTP v4 would be preferable.
How does Secure Timer related to NTP v4?
Was this ever resolved, figured out? I need to also use NTLM.