Library.io component updates

[troydjEPMYB]

I downloaded a component symbol, footprint and 3D model from snapeda. Symbol and Footprint in one lbr file, while the 3D model is a separate file. Now when I upload the component lbr into library.io, and then update the 3D model for the package and save it, I can see that I now have a v2 of the package. However, adding the new component into my design in Fusion 360, it is not seeing the 3D model (it is still seeing only the initial v1 version of the component without the 3D model). I have to then save the component again as a Fusion 360 library component, and then push the new component back to library.io. It seems like a very non-intuitive way to manage components and different versions between Library.io and Fusion 360. Is this convoluted library and component update workflow by design or am I doing something wrong ? In my opinion, I should not have to save the new component in Fusion 360 library manager to see the updates already made in library.io.

[AlinaPeng · Accepted solution]

Hi @troydjEPMYB ,

Sorry to hear that you're having trouble with this workflow.

The root cause for this issue is you modified the 3d model and saved a new version for the 3d package in the library.io site, but the managed library is still link to the old version of the 3d package (without 3d model) rather than the latest version. Right now the managed library is not link to the latest version of the 3d package automatically as we don't know if user really want to reference the latest version of the 3d package in the library.

What you need to do is go to Fusion, edit the managed library, switch to the "packages" tab and update the package to the latest (It will show update icon next to the package, just click it to update) then push a new version to make sure the managed library is link to the latest version of the 3d package. 

I hope it can help you to figure out the workflow a little bit. Sorry for the confusion here!

Best regards,

[troydjEPMYB]

Your solution is basically what I eventually had to do to make the new version with the 3D model available. Apparently, you basically end up with the component is two places, Fusion 360 and Library.io. I would have thought that Fusion 360 would just pull from library.io without having to maintain two copies of the same component in different places. Does this mean that eventually library.io will be deprecated in favor of Fusion 360 native library manager ?

[AlinaPeng]

Hi @troydjEPMYB 

The components stored in the library.io site can be widely used, it allow user to use pubic 3d package form other author or use private 3d package from the same managed folder even when those 3d package may comes from different Fusion team hub. 

I understand you feel like that the workflow is not intuitive if update package in the library.io site. I would recommend you to upload both the lbr file and 3d model file into Fusion. If you make changes to the 3d package in Fusion, the library will always use the latest version of the 3d package.

Best regards,

[jorge_garcia · Accepted solution]

Hi @troydjEPMYB,

I hope you're doing well. We are now in a moment of transition with the libraries, we are working hard to simplify the whole experience because we recognize that having to juggle these different library types creates confusion. Library.io is not going anywhere, it affords some very strong advantages over the Fusion Team libraries. We ask you to just bear with us while we get this sorted.

Best Regards,