PIO Core 6.1.14 Issue compiling with EspAsyncWebServer about platformio-core HOT 9 CLOSED

pio upgrade --dev failed but gave instructions on how to upgrade from command line. Success. Now running PIO Core 6.1.15a1. Project compiles correctly when referencing our branch of ESPAsyncWebServer. Thank you for the quick fix!

from platformio-core.

Note we branched ESPAsyncWebServer and AsyncTCP to our own repository to workaround a bad update in AsyncTCP.cpp released by ESPHome. We've been using our branched/patched version for 2 months without issues.

from platformio-core.

Could you provide a simple project (ZIP archive attached to this issue as a comment) to reproduce the problem?

from platformio-core.

Adding lib_ldf_mode = deep+ to build flags makes no difference. It still can't find AsyncTCP.h.

from platformio-core.

Could you provide a simple project (ZIP archive attached to this issue as a comment) to reproduce the problem?

I'll attempt to strip the project down.

from platformio-core.

Update: it appears the failing project references a library in platformio.ini but doesn't call it in code yet. I have a similar project that does use #include <ESPAsyncWebServer.h> and it compiles properly.

from platformio-core.

MFSB2.zip

Note the project references a custom branch of ESPAsyncWebServer but doesn't actually call the include header. This project will fail to build.

Edit: is this an Uno Reverse card? The build system tries to link a library that isn't used?

from platformio-core.

Thanks for the provided project. The issue was linked with the nested dependency declared via VCS repository. See https://github.com/MicroframeDev1/ESPAsyncWebServer/blob/v3.1.0/library.json#L28

The solution is to avoid using VCS declarations, especially for nested dependencies. You can try a direct branch https://github.com/MicroframeDev1/ESPAsyncWebServer , it contains valid dependencies declared via semantic versioning.

from platformio-core.

You can also re-test this issue via pio upgrade --dev.

from platformio-core.