Update Boards version number to a different version and then change back may not work. #2028
Open
3 tasks done
Labels
type: imperfection
Perceived defect in any part of project
Describe the problem
Suppose I have the Teensy board types installed, like 1.58.1, and I did a few builds, and then decide I wish to try something out on the current beta build 0.59.2. Run a test or two, then decide to update back to 1.58.1
And now the builds fail.
The problem is that the tool Teensy.exe was running when I installed or reinstalled the different versions.
To reproduce
Update from to 0.59.2 The output window shows:
Now I convert back to 1.58.1
I then try building the same sketch over again and see:

So I looked in the tools directory and all that was init was:

My first thoughts were, that my Anti-virus decided to quarantine the new files for some reason. So it took several minutes for me to figure out how to see what was currently quarantined and the list was empty.
So I am now believe what happened is that when it installed the new version of tools, it tried to remove the other version, and failed to remove open executable. And then when I asked it to reinstall that version, it saw the directory existed and assumed everything was fine.
Expected behavior
One or both of:
a) when it tried to remove the previous version and failed, it should give me some type of warning and better yet let me know that the app Teensy is running, and give me a chance to do a retry.
b) When it detects that the tools directory existed, do a sanity check, like the package contained N object but the current one only has 1 in it...
Arduino IDE version
2.1.0
Operating system
Windows
Operating system version
11
Additional context
I did a quick search and did not find anything.
I resolved it this time, but closing the teesy.exe application, and change versions twice again and this time it removed the old version and the whole tools directory.
@PaulStoffregen - not sure anything we can do for this on the Teensy Side/
Issue checklist
The text was updated successfully, but these errors were encountered: