I'm using an Arduino 33 IoT and setting it up on the IoT cloud. I've tried three different boards but when I go to load the sketch to the com port from the IoT cloud platform it throws the same error.
Any advice would be greatly appreciated. None of the devices came online after they were configured so loading sketch via com port.
Thanks,
Veronica
Error as follows:
Start verifying
Error during build: loading library from /mnt/create-efs/webide/74/67/7467ab80d8ecdf7af859529712db6778:datahead2023/libraries_v2/tmp1696196991259678221: invalid library: no header files found
Error during build: loading library from /mnt/create-efs/webide/74/67/7467ab80d8ecdf7af859529712db6778:datahead2023/libraries_v2/tmp1696196991259678221: invalid library: no header files found
Update: This error is occurring on all sketches on the Iot cloud. Even the things that were working previously. Seriously ready to go back to the regular Arduino IDE. Very frustrating.
Hi @datahead2023. I apologize for this. I have notified the Arduino Cloud team about the problem. I'll circle back here if I have any news.
Until then, I do think the best available workaround is to use Arduino IDE for compiling and uploading sketches. You can use Arduino IDE to develop Arduino IoT Cloud Thing sketches, and Arduino IDE 2.x even has an integration with your Arduino Cloud sketchbook. You can continue to use your dashboards on the Arduino Cloud website even with the devices running the Thing sketches you developed with Arduino IDE.
Hi @datahead2023. The problem should now be fixed. Please try using Arduino IoT Cloud again now, just as you did before when you got that "invalid library: no header files found" error.
Please let me know if you still experience any problems.
Good Morning,
Yes that seems to have solved the issue. Thank you for your prompt attention regarding this issue.
So I'm curious, what was the actual problem and what can I do (If I did something to cause this) in the future to avoid this from happening again? Have a blessed day.
Thanks,
Veronica
Arduino Cloud uses a tool named "Arduino CLI" to compile your sketches. The version of Arduino CLI used by Arduino Cloud was unnecessarily strict about the installed libraries. The intention was that it would only print a warning when it detected that you have an Arduino library installed that doesn't have a valid format, but a bug caused it to instead cancel the compilation when an invalid library was present:
I don't know the details, but previously under certain conditions the Arduino Cloud library management system could generate an empty temporary folder in the folder where your custom libraries are installed, like this folder shown in the error message you encountered:
So the fault you experienced is produced by a combination of a bug in Arduino CLI and a bug in the Arduino Cloud library management system.
You didn't do anything to cause the problem. The creation of the invalid library was caused by a rare random glitch in Arduino Cloud. Since the Arduino Cloud developers have already made a fix, I don't think you will encounter this problem again. If it does please report it here on the forum and the Arduino Cloud developers will be sure to investigate and fix the problem.