ESP32 + Firebase: Firebase.begin loop and Queues example not working

Hi people. I'm new here, my first post. I'm using:

  • ESP32 Dev Kit
  • Platformio
  • Arduino framework
  • Espressif32 platform
  • Firebase Library 4.4.8

I'm developing some test project with Firebase library and I have two problems that I'm not sure how to solve after reading the documentation.

Question 1:
If there is no WiFi nor internet when I call Firebase.begin(&Config, &Auth) it keeps in a loop waiting for connectivity and thus the rest of the code is not being executed. I followed the basic INO authentication example. Log from console:

Token info: type = id token (GITKit token), status = on request
Token info: type = id token (GITKit token), status = error
Token error: code: -4, message: connection lost
Token info: type = id token (GITKit token), status = on request
Token info: type = id token (GITKit token), status = error
Token error: code: -4, message: connection lost
Token info: type = id token (GITKit token), status = on request

And so in a loop. Is there a way to config the library to avoid this?

Question 2:
I tried the INO Queues example (https://github.com/mobizt/Firebase-ESP32/tree/master/examples/Queue) to test what happen when internet connection is lost but the example not entering Queues. When it ask for turning off the WiFi, and doing so, an error message show up and nothing happens to Queues and its count value is zero.
Log from terminal:

--------------------------------------------------------------------------
To test error queue, turn off WiFi AP to make error in the next operation
--------------------------------------------------------------------------

[ 22157][E][WiFiClientImpl.h:347] tcpConnect(): connect on fd 48, errno: 113, "Software caused connection abort"
Get double... token is not ready (revoked or expired)
Get blob... token is not ready (revoked or expired)

So the example does not process the queues and nothing happens when the internet returns.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.