Closed cfficaurzua closed 2 years ago
It is the NTP time requesting process and no timeout because it's not blocking process.
It will stay at that process when the device time was not set yet.
You should check your internet connection (not WiFi).
Or you can set the device time manually before calling Firebase.begin
and make sure you get the valid timestamp from calling time(nullptr)
.
There are many examples on internet for device time setting from NTP server and RTC.
I recommended you to update the library to v3.15.8.
This is the important update to fix stream and token initialization issues.
The token initialization process is now can be resumed when the internet connection lost and the timed out error during NTP server time synching will be reported.
Much appreciated
I recommended you to update the library to v3.15.8.
This is the important update to fix stream and token initialization issues.
The token initialization process is now can be resumed when the internet connection lost and the timed out error during NTP server time synching will be reported.
Sometimes it works just fine
but sometimes it get stuck at
Sometimes it takes 5 min, but sometimes I wait more than an hour with no response. Is there anyway I can put a timeout?
Thanks