Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send_Message examples throw missing header files error (ESP8266) #1

Closed
reinlten opened this issue Jan 14, 2021 · 6 comments
Closed

Comments

@reinlten
Copy link

Hey, Im using Arduino Uno to program ESP8266 to send messages to my phone via FCM.
After inserting all keywords i got the following error for both the legacy and HTTPv1 examples:

C:...\Firebase-ESP-Client-main\src/Firebase_ESP_Client.h:42:17: fatal error: No such file or directory
#include <ETH.h>

I editet the file "Firebase_ESP_Client.h", so that ETH.h will not be imported. The program compiled properly.
I got it working for the HTTPv1 Protocol, but not for legacy, but its possible that there are non related problems.

@reinlten reinlten added bug Something isn't working good first issue Good for newcomers invalid This doesn't seem right wontfix This will not be worked on labels Jan 14, 2021
@stale stale bot removed wontfix This will not be worked on labels Jan 14, 2021
@mobizt mobizt removed bug Something isn't working good first issue Good for newcomers invalid This doesn't seem right labels Jan 14, 2021
@mobizt
Copy link
Owner

mobizt commented Jan 14, 2021

This library is for ESP8266 and ESP32.
You need to install the ESP8266 Core SDK and choose the ESP8266 board.

@mobizt mobizt closed this as completed Jan 14, 2021
@mobizt
Copy link
Owner

mobizt commented Jan 14, 2021

Ok you are right I accidently edit the source to include ethernet to test but forgot to remove it when publish.

@mobizt
Copy link
Owner

mobizt commented Jan 14, 2021

The library updated.
The legacy API, you need to use Server Key from Firebase console.

@reinlten
Copy link
Author

Okay thanks.
I have both the server key and device token inserted and it didn't work, however HTTPv1 works fine for me.

@mobizt
Copy link
Owner

mobizt commented Jan 14, 2021

The legacy FCM works normally. Please check the example.
You may provide invalid server key which this already stated in the Firebase FCM document.

@mobizt
Copy link
Owner

mobizt commented Jan 14, 2021

The HTTPv1 uses OAuth2.0 for authenticate while the legacy API authentication uses the sever key as in the old 2 years library and no problem with that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants