Library.IO issues when uploading models

[sndstrmDE]

When opening the 3D Editor following error message (sometimes) pops up for a part of a second (if the interface is not reloaded before even showing the error):

Package generator does not show up in Editor. When dropping a file in the Editor the whole web container gets replaced by the file, so showing the STEP as plain text or even displaying regular images.

Tried to view the library online. Worked for the first time, then got caught in a redirect loop between library.io and https://contapi.circuits.io/123D-Circuits/actions/login?tenant=circuits&redirect=https://library.io/... due to 401/403 errors (regarding the console, see video).

[sndstrmDE]

Upload issue seems to happen only with libraries I copied from managed to local and then reupload to add 3D-Models like con-phoenix-762.lbr / urn:adsk.eagle:library:177 (now my urn is urn:adsk.eagle:library:9053057) but web redirect loop happens now with all library.io pages where you have to be signed in.

[sndstrmDE]

Resolved my issue by importing a local lbr from Version 8.0.2.

But still reproducible when trying to add models to a managed library:

Select a (public) managed library -> Right Click - Copy -> Save in local library directory -> Create managed library

After the upload is finished I can open the library (under my managed libraries) as usual, but opening a 3D Package has the same bugs:

- No Package Generator

- Replacement of the web container when dropping files to upload

- Import from local 3D package/web does not import any 3D Package

It's sad that there is the feature to create a 3D model of your PCB but almost all system libraries (managed by Autodesk) have no 3D models.

[david.mellis · Accepted solution]

The package editor will open in read-only mode for 3D packages copied from public libraries, since we retain the identity/URN of the original 3D package (to allow you to pull in updates when they happen). We're working on a simple workflow for forking the 3D package so that you can edit it. In the meantime, as a work-around, you can make a small change to the footprint and then create a new version of the managed library. This will fork the 3D package and you'll be able to edit the new, forked package. 

We're continuing to work on adding 3D models to our existing libraries. Any suggestions for components / packages you'd like to see us add 3D models for?