Authenticating results in error code 400 - but Firebase does recognize my login

[Sulomus]

I am trying to authenticate (log in) using exact replica of example code from ESP32 Client library (the new version)

• When I run my code I successfully connect to WiFi and also I can
  successfully CREATE new account from the ESP32 board (using the signIn() method).
• When the account is created - method Firebase.authenticated() returns False.
• The same happens when I try to only log in - Firebase.authenticated() returns False again.
• I need to know if my log in or registration was successful.
• In my Firebase authentication signup with email/pass is enabled.
• I know there was a similar GitHub issue here. But the problem was in firebase rules - my rules are open (see below).

In my serial monitor I can read that the error code is 400:

Code that I am using:

Serial.printf("Firebase Client v%s\n\n", FIREBASE_CLIENT_VERSION);

/* Assign the api key (required) */
fb_config.api_key = API_KEY;

/* Assign the user sign in credentials */
fb_auth.user.email = email_name.c_str();
fb_auth.user.password = email_name.c_str();

/* Assign the RTDB URL */
fb_config.database_url = DATABASE_URL;

Firebase.reconnectWiFi(true);
fb_do.setResponseSize(4096);

/* Assign the callback function for the long running token generation task */
fb_config.token_status_callback = tokenStatusCallback; //see addons/TokenHelper.h

/** Assign the maximum retry of token generation */
fb_config.max_token_generation_retry = 5;

/* Initialize the library with the Firebase authen and config */
Firebase.begin(&fb_config, &fb_auth);

if(Firebase.authenticated()){
  Serial.println("I am authenticated");
} else {
  Serial.println("Well I AM NOT???");
}

Screenshot from my Firebase authentication that my ESP32 was created and also logged in today:

I know my Firebase initialization was successful because I can read and write read data into the Realtime database:

I am using PlatformIO and this is my config file:

[env:esp32dev]
platform = espressif32
board = esp32dev
framework = arduino
monitor_speed = 115200
build_flags = -D PIO_FRAMEWORK_ARDUINO_MMU_CACHE16_IRAM48_SECHEAP_SHARED
lib_deps = 
	mobizt/Firebase Arduino Client Library for ESP8266 and ESP32@^2.5.4
	bblanchon/ArduinoJson@^6.18.5

Other links:

• My original Stack overflow question.

Firebase RTDB rules:

{
  "rules": {
    ".read": true,
    ".write": true,
  }
}

[mobizt]

It's not related to security rules in Firebase, issue #135 is not not actually related to the rules.

No logs for this because it's the googleapis RESTs API by providing the request with user credentials and it returns id token for authentication, that's it.

There are invalid authentication credentials you provided in this case it can be api key (web api key) if the email and password are ok.

In this case you can try to setup new project and test it, it should ok.

[mobizt]

What do you expected for this fb_config.signer.signupError.message.c_str() when sign in?

[mobizt]

Sign up is not sign in.

[Sulomus]

You should update the ESP32 Core SDK.

Could you please provide a link or docs on how to do that?

[Rishabh110204]

Brother, I have a similar issue can you resolve it?

ERROR:
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

#define DATABASE_URL "XXXXXX"
#define API_KEY "XXXXXX"

FirebaseData fbdo;
FirebaseAuth auth;
FirebaseConfig config;

unsigned long sendDataPrevMillis = 0;
bool signupOK = false;

void setup part :

if (Firebase.signUp(&config, &auth, "email", "password")){
Serial.println("ok");
signupOK = true;
}
else{
Serial.printf("%s\n", config.signer.signupError.message.c_str());
}

config.token_status_callback = tokenStatusCallback; // see addons/TokenHelper.h
Firebase.begin(&config, &auth);
Firebase.reconnectWiFi(true);

if(Firebase.authenticated()){
Serial.println("I am authenticated");
} else {
Serial.printf("Error occured: %s\n", fb_config.signer.signupError.message.c_str());
}

loop part :
if (Firebase.ready() && signupOK && (millis() - sendDataPrevMillis > 5000 || sendDataPrevMillis == 0)){
sendDataPrevMillis = millis();
sendDataToGoogleSheets(t1, t2, t3, t4, t5, h1, statusDI1, statusDI2, statusDI3, statusDI4, au16data[12]);
}

function :

void sendDataToFirebase(float ot, float lvt, float lv1t, float lv2t, float hvt, float hum, int otha, int lvtha, int gora, int moga, int rly1) {

if (Firebase.RTDB.setFloat(&fbdo, "realtimedata/ot", ot) && Firebase.RTDB.setFloat(&fbdo, "realtimedata/lvt", lvt) && Firebase.RTDB.setFloat(&fbdo, "realtimedata/lv1t", lv1t) && Firebase.RTDB.setFloat(&fbdo, "realtimedata/lv2t", lv2t) && Firebase.RTDB.setFloat(&fbdo, "realtimedata/hvt", hvt) && Firebase.RTDB.setFloat(&fbdo, "realtimedata/hum", hum) && Firebase.RTDB.setInt(&fbdo, "realtimedata/otha", otha) && Firebase.RTDB.setInt(&fbdo, "realtimedata/lvtha", lvtha) && Firebase.RTDB.setInt(&fbdo, "realtimedata/gora", gora) && Firebase.RTDB.setInt(&fbdo, "realtimedata/moga", moga) && Firebase.RTDB.setInt(&fbdo, "realtimedata/rly1", rly1) ) {
Serial.println("PASSED");
}
else {
Serial.println("FAILED");
Serial.println("REASON: " + fbdo.errorReason());
}

}

Please help me out...

[mobizt]

@Rishabh110204

In your case, the email you assigned does not belong to any user in your authentication provider of your Firebase project.

[mobizt]

You should follow the examples first.

This variables must be assigned global
FirebaseAuth auth;
FirebaseConfig config;

[mobizt]

I may miss your point as your two paragraph are contrast.

between this
In my serial monitor I can read that the error code is 400

and this
I know my Firebase initialization was successful because I can read and write read data into the Realtime database:

[mobizt]

Why use delay and expected the no delay result?

[mobizt]

You are blocking the authentication process as it runs on main task.

[Sulomus]

Man thank yo very much! The problem was that I was checking the authentication too early. When I check it now in the loop() after some time it turns to True!

[mobizt]

In the version 2.5.3 and earlier, in ESP32 using delay in loop will not affected the authentication process because it created another RTOS task for this.

I finally found the memory leak issue in TCP client that runs in that task when WiFI was disconnected and remove the RTOS task for token generation and leave it runs on main RTOS task to reduce the memory reserved for task and memory leaks issue.

[Sulomus]

Yeah that makes sense. Thanks very much again! Keep up the amazing work.