New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kronos not working on cellular data but only on Wifi? #52
Comments
It definitely should work on cellular. We use it at lyft on production. Can you debug a bit more your case and provide more information about where it breaks? |
So, I have found out the following: If I use an NTP pool with just one entry: "0.pool.ntp.org" then everything works as expected. Any ideas? |
@agforte is this still an issue? It would definitely prevent me from using this framework in my project |
This is not an issue. We had been running Kronos in production at Lyft for
a long time now
…On Fri, Apr 24, 2020 at 12:28 PM Adam Lowther ***@***.***> wrote:
@agforte <https://github.com/agforte> is this still an issue? It would
definitely prevent me from using this framework in my project
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABYVMN6HWYEVBGRO45XRK3ROHR4LANCNFSM4G6SPS3A>
.
|
Feel free to submit a new issue with more specifics if you're still seeing this! |
It looks like Clock.sync() does not work if I have WiFi off and cellular data (LTE) on. In particular, the "first:" and "completion:" blocks never get called. It works if WiFi is on.
Am I missing something? It seems rather odd.
The text was updated successfully, but these errors were encountered: