I hereby certify that I am not simply asking someone else to design a footprint for me.
After getting some help on my questions about footprints, I’m working on preparing my first KiCad schematic for the PCB design. I’ve run into an issue with a disappearing footprint along the way.
I downloaded KiCad within the past 6 weeks and got version 8.0.4 for macOS. While looking for footprints, I saw a number of ESP32 footprints, but none for the Devkit C version, which is quite a different form than the simple footprint for the chip by itself. I did some searching and found a footprint online and imported it into my library and checked it out. It imported okay and I picked it as a footprint for my schematic. I did a test run and when I tried to import the schematic into the PCB editor, there were no errors specifying the ESP32 chip.
Then, within the past week, I updated KiCad to 8.0.5. I don’t know if that’s why I’m having this issue or it’s something else, but now the footprint for the ESP32 Devkit C is no longer available in my library.
Is this normal after an update? Do I need to create my own custom library and save it somewhere so imported footprints don’t get clobbered by an update? What should I do to deal with this so I don’t lose imported footprints in the future?