Issue is still there AFAIK. It will come up every time you have an open project that is configured to use a programmer/debugger that is currently not present.
 
For example, i use an ICD3 and a PK4 for development. I'm currently using a PK4, but then i switch to another project where i need to grab the ICD3, so i disconnect the PK4 and attach the ICD3. Close MPLABX. Open it again, when loading both projects the one that require the PK4 will complain that tool noID is missing.
 
This "issue" came after they decided to change how the tools are displayed in a project configuration:
before you would see the complete list with red/yellow/green dots. In 5.10 they decided to only show the tools supported by the part and ONLY if said tool was connected. the ONLY part is what's causing the issue

hello folks,
 
I have faced the same issue on Ubuntu 20.04 with MplabX v5.40 (XC8-2.30).
 
The error message
 
    The project uses platform tool noID but that tool is not installed. From the main menu, select Tools then select     
    Plugins. Install the missing plugin.
 
was printed all the time when I re-started the tool. Later, once I tried do anything with the active project (clean, re-build or just open MCC), the whole MplabX was looking frozen. Nothing has happened after waiting 2-5 min. I only could xkill the tool. I agree the "noID" tool name what might be missing is not an informative text, it woudl be much better to print what is really missing.
 
Anyway, I have a workaround on this. My project was using Pickit3 as programmer/debugger, but at this morning, the Pickit3 was not connected. The above mentioned error message has been stopped to print after restarting MplabX.
 
br,
/Robi 

noID comes out BECAUSE you selected a tool that is now not available. The new default behavious is not of defaulting to "no tool" tool but remaining to the selected tool and warn you about that.

hello,
After playing around with this issue, I have upgraded my MplabX to v5.45 and also started to use XC8 v2.31. So now, the "message" does not come with/without Pickit.
 
And yes, I am using Ubuntu 20.04 64 bit OS within VMWare as a guest OS on Windows 10 host
    Linux ubuntu 5.4.0-58-generic #64-Ubuntu SMP Wed Dec 9 08:16:25 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
 
On the other hand, the version 5.45 of MplabX is not really stable (I guess this was not deeply tested/verified)
- It hangs often when I start/stop MCC on a project. The WA I found is to "kill" MplabX (because exit also does not work at this time).
- Pickit not always detected if that connected. I need to restart the tool few times after each for start using Pickit
 
So, I think a bit more test would be good to be done before releasing. I can imagine to send new release for "beta testers" before make a real release, or other alternative way would be good to use just to minimize the "trivial" faults.
 
thanks,
/Robi