Unable to renew the token automatically when use Firestore

[edwardchuang]

Working on a long-running service and send heartbeats every 60 seconds by creating a Firestore document.
However, it seems the authentication token will be expired and not automatically refreshed after default 3600 seconds (1 hour)
Error message:

Missing or invalid authentication.

Digged some old discussions but none of those workarounds are working. I tried to force a refresh by

  config.signer.lastReqMillis = 0; 
  config.signer.tokens.expires = 0;

With no luck. Any clue?

Setup:

Board: ESP32 (Adafruit ESP32 Feather V2)
SDK Version: 4.3.0
IDE: PlatformIO IDE 3.0 for VSCode 
PlatformIO Core 6.1.5

[mobizt]

[mobizt]

Firebase-ESP-Client/examples/Firestore/CreateDocuments/CreateDocuments.ino

Line 123 in 04eff0e

// Firebase.ready() should be called repeatedly to handle authentication tasks.

[mobizt]

Hello Edward,

Thanks for choosing me for Google Open Source award.

The function Firebase.ready() should be called repeatedly in loop to handle authentication tasks.

[edwardchuang]

Arrgh, yes. I think I followed the example correctly, am I ?

void loop() {
  const int buttonClicked = (digitalRead(BOARD_BUTTON_PIN) == LOW) ? true : false;

  if (Firebase.ready() && (millis() - lastMillis >= 60*1000UL || lastMillis == 0))) {
    lastMillis = millis();
    sendHeartBeat();
  }

  (do something else)

  yield();
}

Unfortunately I don't have JTAG on hand so I can't set some breakpoints for further debugging ...

BTW, it's my great honor to nominated you for the award and glad you earned it!
Once again thanks for such wonderful and great work!

[mobizt]

That is a bug also found in this issue #461.

I have updated the library to fix this bug, please update the library.

Thanks for addressing the issue.

[edwardchuang]

Thanks for the prompt reply and I did updated the library to 4.3.2 (clean install, of course)
But it seems the session expired after one hours and the problem still exists. Any idea?

[mobizt]

The token will be refresh in 55 minutes by default. The Firebase.ready() should be executed in time i.e., within 55 minutes since token generated.

You should make sure that no other codes that block the Firebase.ready() from execution.

If your device time was synched with NTP server or manually set after Firebase.begin, you should call Firebase.begin again to reset the authentication. This is because the time(nullptr) will return the seconds count instead of timestamp when your device time was not synched or set. Then token expiry time is based on the seconds count instead of timestamp in this case.

To test Firebase,ready function to work, you can place this option in setup or anywhere to refresh the token in 1 minute.

config.signer.preRefreshSeconds = 3600 - 60;

Edit: seconds count instead of milliseconds count

[edwardchuang]

Thanks. I do review your commit in #461 and add -DESP32 in build_flags of platformio.ini just out of curiosity. Now it seems triggering token refresh and expiration does not happend now.

Heartbeated. [r15UAp4MoTS3CCFBKj7h]
Token info: type = id token (GITKit token), status = on refreshing
Token info: type = id token (GITKit token), status = ready
Heartbeated. [hHhIsBPXmGqwwMSICTjf]
Heartbeated. [EmKNgP2qiIAwO6cBY4tG]
Heartbeated. [hpqaIruPQ51HDPLKaize]
Heartbeated. [tZFFTnqN746muylSeq3r]
NTP synced, the current date/time is: 2023-01-08T16:23:17+08:00
Heartbeated. [tFT7JUi660SMd7is7qHc]
Heartbeated. [UOlMq6lbDOCqwgrDXVVE]

The token had refreshed five minutes before the expiry (1 hour, 16:23 local time) mark, seems working as intended.

That's weirdo but so far so good.
Will keep you posted if there's something goes wrong again. Thanks for your help!