arduino/arduino-ide

Arduino Library Update won't delete older library folders when updating

Opened this issue · 0 comments

Describe the problem

Hello IDE Team.

Arduino library updates are still a little rough for me, and have been for quite some time. Long ago, library updates were simpler.
When manually updating a library using the IDE, the older library folder is not replaced. It causes an error and fails until I manually delete the older folder.

I am running:
Windows 11 Pro 23H2
Fully configured AMD Ryzen 9 6900HX with Radeon Graphics with 32 GB Ram
IDE 2.3.4

When I attempt to manually update an existing Arduino library, I always have to delete the old library folder to make the update work.
Here’s a partial screenshot of my library folder.

This example is for library SensorLib. It shows the SensorLib library folder in within the library folder before I try to update it.
Image

First: Arduino IDE tells me to update the library.
I hit the UPDATE (SensorLib) button and get the error messages in the screen shot below.
Image

Then, I delete the SensorLib folder in my library folder and hit the UPDATE button again.
Now the library updates without error, as shown in the screenshot below.
Image

However, it also leaves a folder named package-xxxxxxx behind, which I have to manually delete. See screenshot below.
Image

This is a minor nuisance, but not a showstopper. This behavior has been around for a long time, but at one time, libraries updated more easily, without the need to delete the older library folder.
Please tell me if you want additional information. I am happy to help.

Thanks for keeping IDE updated and constantly improving. I remain a fan and a donor to the cause.

To reproduce

Manually update any library using IDE 2.3.4 without deleting the library folder first.

Expected behavior

Error message belowImage

Arduino IDE version

2.3.4

Operating system

Windows

Operating system version

11 Pro 23H2

Additional context

No response

Issue checklist

  • I searched for previous reports in the issue tracker
  • I verified the problem still occurs when using the latest nightly build
  • My report contains all necessary details