So I've noticed editing a Library.io managed library creates a "Team" copy in the fusion 360 cloud file system. This copy takes precedence over the Library.io copy, and essentially hides the Library.io copy when you access Library Manager. Deleting the "Team" library in this cloud file system reverts the associated library in Library manager to the "Library.io" library.
Now I am certainly facing a bug, seeing I have a Capacitor "Team" library showing up Library Manager, however it is not found in the fusion 360 cloud file system. So I cannot delete it to revert back to a Library.io verision. Trying to edit the "Team" version through Library Manager will actually crash Fusion360 every time. (Components from the library can still be placed into a schematic)
On the same note, perhaps, someone can explain a bit about Library precedence and best practices, or link some documentation on this subject. I remember I had several issues with importing local EAGLE library, most of which I can't replicate in my memory. Most of which have been solved by using uploading my custom libraries to Library.io. I remember a time when I would edit them in EAGLE and sync with Library.io so no duplicate "Team" version is created in the Fusion360 cloud file system, as the Team/fusion 360 cloud local copy, would cause confusion and conflicts. It seems "Team" version on Fusion 360 cloud file system are properly syncing with Library.io now, for the most part. The bug with the Capacitor library is still outstanding of course.
Fusion
