Conflict with Teams library and Local lib used "in Design" but not valid

Conflict with Teams library and Local lib used "in Design" but not valid

relaxmax01
Participant Participant
343 Views
0 Replies
Message 1 of 1

Conflict with Teams library and Local lib used "in Design" but not valid

relaxmax01
Participant
Participant

Seems I'm not only one struggling with library.io, Teams lib and local lib. Here is an issue or question I'm hoping someone has found a way to solve:

 

I have created my own managed library as a F360 Teams lib. This is synch'ed on library.io on my managed folder no problem (all good so far). In my schematic, I have probably a (few) "rogue" component(s) pulled from my local lib before I moved that lib to .io/Teams. The library manager shows my managed lib (name MaxManagedlib) twice: one as Type "Teams", the second as local with a warning stating "Library not available".  - Screenshot added

 

is there a way to find in my schematic which component belongs to that local or invalid lib so I can replace with the proper one from my managed lib?

or can I remove that broken reference to the lib so it doesn't show up in the library manager?

 

hope the question makes sense.

0 Likes
344 Views
0 Replies
Replies (0)