Michael Sanders
Michael Sanders
@DaveWoodCom thoughts?
@Visput: Good point. NTP doesn't support this level of precision but we can update the data types used internally to at least maintain what is returned by the initial system...
@JoshLorDeveloper: This should work as expected (backgrounding the app and changing the system clock should have no effect on TrueTime). Can you post your example project here?
Not currently, but this is actually the next feature in the pipeline. [TrueTime for Android](https://github.com/instacart/truetime-android) currently does (as-of https://github.com/instacart/truetime-android/pull/15) so we'll probably be copying the method used there.
Once `start` is called, TrueTime internally starts fetching a reference time, and automatically pauses/restarts upon receiving reachability events. The `retrieveReferenceTime` function blocks waiting for the fetch to complete. If we...
- `start` only needs to be called once (e.g. at app launch). The library will automatically pause/restart depending on network conditions. There's no need to call it again unless it's...
Hiya. I will have to think about this some more. The reasoning behind it being a separate method from `start` is to distinguish between starting the NTP sync (which can...
:+1: Yep that's right, or it can be called multiple times, in which case it will just return immediately with the cached time.
@otymartin That is correct, until #9 is implemented.
@yehoshuanagel: Thanks for the report. What version are you seeing this on?