Token info infinite loop on error

[Cintet00]

Hey there.

I'm experimenting with this Arduino library, testing the examples and using a token to authenticate. I do it using:

Firebase.setIdToken(
            &FireConfig,
            "",
            3600 /* expiration time */,
            token
 );
    

It works Ok but sometimes I get a token error, and console output shows this in a loop:

Token error: code: 400, message: bad request
Token info: type = id token (GITKit token), status = on request
Token info: type = id token (GITKit token), status = error
Token error: code: 400, message: INVALID_EMAIL
Token info: type = id token (GITKit token), status = error
Token error: code: 400, message: bad request
Token info: type = id token (GITKit token), status = on request

I think that's the callback: FireConfig.token_status_callback = tokenStatusCallback;

When this endless loop happens I lose control and it doesn't return to loop(). I tried to use the WDT along esp_task_wdt_reset() inside loop() but it doesn't work either since there is no reset by WDT.

What can be done to avoid entering this infinite loop in case of this error? Even if the infinite loop is generated, shouldn't the WDT reset the ESP32?

This is WDT configuration in setup():

  esp_task_wdt_init(10, true);   //enable panic so ESP32 restarts
  esp_task_wdt_add(NULL);       //add current thread to WDT watch

[mobizt]

I think you incorrectly use or provide invalid parameter to the function setIdToken.

Please make sure you understand the information that provided in the example.

Firebase-ESP-Client/examples/Authentications/SignInWithIDToken/SignInWithIDToken.ino

Lines 126 to 130 in f17ea76

	/* Set ID token */
	// The ID token obtained from other apps e.g. Firebase Admin.
	// The Refresh token for token refreshment which used when token was expired.
	// If Refresh token was not assigned or empty string, the ID token will not refresh when it expired.
	Firebase.setIdToken(&config, "<ID Token>", 3600 /* expiry time */, "<Refresh Token>" /* refresh token */);

There is no blocking process in the library and the error showed from the callback is from the token processing task as long as you call Firebase.ready in loop.

Then it is not possible that the main loop will never execute when the token callback reports the error.

The token processing task behind the Firebase.ready works as state machine which will exit the task when error occurred or run through the sequences (step by step) until finished when no error.

[Cintet00]

Hi mobizt

I think you incorrectly use or provide invalid parameter to the function setIdToken.

I'm sending to the ESP32 via bluetooth the refreshToken from an Ionic app after authenticating the user. The JSON after authenticating in the app is like this:

{
  "uid": "uidapp",
  "email": "useremail@emailserver.com",
  "emailVerified": true,
  "isAnonymous": false,
  "providerData": [
    {
      "providerId": "password",
      "uid": "email@email.com",
      "displayName": null,
      "email": "useremail@emailserver.com",
      "phoneNumber": null,
      "photoURL": null
    }
  ],
  "stsTokenManager": {
    "refreshToken": "***this short token is sent using bluetooth to esp32 for firebase login***",
    "accessToken": "long access token",
    "expirationTime": 1709166087975
  },
  "createdAt": "1679071604487",
  "lastLoginAt": "1707148762594",
  "apiKey": "apiKey",
  "appName": "[DEFAULT]"
}

The refreshToken is sent to be used in Firebase.setIdToken() on the ESP32. This works perfectly most of the time.

There is no blocking process in the library and the error showed from the callback is from the token processing task as long >as you call Firebase.ready in loop.

Then it is not possible that the main loop will never execute when the token callback reports the error.

The token processing task behind the Firebase.ready works as state machine which will exit the task when error occurred or >run through the sequences (step by step) until finished when no error.

I will investigate why I'm stuck in a loop when the error appears. I'll post again here if I find anything about it this week.

Thank you

[Cintet00]

About the infinite loop I think I got it. Firebase.ready() can be true if there is wifi but there is no internet connection

[mobizt]

You also should not mix use of authentication methods by providing the following options while using setIdToken in the setup.

Firebase-ESP-Client/examples/RTDB/Basic/Basic.ino

Lines 98 to 99 in f17ea76

	auth.user.email = USER_EMAIL;
	auth.user.password = USER_PASSWORD;

[mobizt]

You should provide both ID token (the second parameter) and the refresh token (fourth parameter) to the function.

If you provide empty ID token, library will consider that you are using Email/Password authentication by default.

[Cintet00]

Mmmmm... I'm sending only the refreshToken to be used with setIdToken... I thought it was enough for login...

[mobizt]

Yes, I forgot this feature.

Firebase-ESP-Client/examples/Authentications/SignInWithRefreshIDToken/SignInWithRefreshIDToken.ino

Lines 128 to 130 in f17ea76

	// Use refresh token and force token to refresh immediately
	// Refresh token is required for id token refreshing.
	Firebase.setIdToken(&config, "" /* set id token to empty to refresh token immediately */, 3600 /* expiry time */, "<Refresh Token>");