Fail to upload library to LIBRARY.IO

[Anonymous]

Hello,

When I try to upload a certain library to LIBRARY.IO, I get this error :

"

Échec de l'importation de la bibliothèque gérée (La transaction a échoué: Error transferring https://contapi.circuits.io/123D-Circuits/libraries/16378166/import - server replied: Forbidden).
Si ce problème persiste, veuillez contacter le support technique et spécifier l'URN de la bibliothèque: urn:adsk.eagle:library:16378166.

"

Best regards

EDIT : I was able to upload the library with Eagle.

EDIT2: I had to unlink the library on Fusion 360 first and after that I was able to upload the library from Fusion 360 to LIBRARY.IO. So problem solved.

EDIT3 : The same trick didn't work with another library, I get this error :

"

Échec de l'importation de la bibliothèque gérée (failed).
Si ce problème persiste, veuillez contacter le support technique et spécifier l'URN de la bibliothèque: urn:adsk.eagle:library:22558159.

"

[colin_taylor]

Hi Manuel,

It looks like you received a forbidden error which means that you did not have permission to write to that specific library.  We have a "Managed Folder" feature which means that every library and component created gets put into one of these Managed Folders.  That folder has an owner and the owner can invite people to read/write from that folder.  So in the future if you run into this issue again you can simply ask the owner of the Managed folder the library lives in to invite you to that Managed Folder and you would then have permission to create new versions of that library.  What you did also works, but the difference is that you ended up with a new library who's lineage is now diverged from the original. Hope this helps!

[Anonymous]

Hello Colin,

Thank you for the explanation. I think I am getting the error again :

"

Échec de l'importation de la bibliothèque gérée (failed).
Si ce problème persiste, veuillez contacter le support technique et spécifier l'URN de la bibliothèque: urn:adsk.eagle:library:22564757.

"

I have attached an image showing that I am the owner of the library. What else could be the problem?

Best regards.

[colin_taylor]

Hi Manuel

I apologize that I didn't realize you mentioned two different libraries in your first post.  Indeed it looks like there were some issues consuming your libraries 22558159 and 22564757.  This is something I'll look into right away and I'll let you know when we have a fix.  As for 16378166, this is a public library.  When I mentioned that you weren't the owner I should have been more specific, I meant you weren't the owner of the Cloud version of the library on library.io.  When you start using a library in Fusion that comes from library.io we put a copy of it in Fusion Team (which you own) and link it to the copy on library.io.  This allows you to make your own edits to the library while still being able to pull any changes that the owner of the library makes on library.io.  If you want to push the changes you made to this public library (the changes you have in Fusion Team) to library.io you need to unlink the library from public one on library.io.  This can be done from the unlink button which is near the push and pull buttons.  Once you unlink and push this library it becomes its own library and is now no longer connected to the public one you initially started with.

[Anonymous]

Hello Colin,

Don't worry I know my first post was a little confusing. For the problem just consider the 22564757, because the 22558159 I think I already deleted.

Perfect, thank you for the explanation, it's clear for me now.

[colin_taylor]

Hi @Anonymous ,

It appears you did some editing of the library outside of the editors.  Unfortunately library.io does not support this.  If you do wish to make manual changes to your assets directly without using the editors you must add locally_modified="yes" to your assets tag, but since we don't support this I can't guarantee it will work in every scenario.  In this case it looks like you manually changed the name of your package "XPLAINED_MINI_UNO". The urn actually matches to a package called "UNO_R3_SHIELD_ICSP", because of this name mismatch your management is failing. If you add <package name="XPLAINED_MINI_UNO" urn="urn:adsk.eagle:footprint:37284/1" locally_modified="yes"> the management should work, but again I recommend you do this in the editors and not manually. 

Hope this helps

[djon_3V3]

Also having this problem.

Looks like the user has to get to some lengths into having things working smoothly, due to some internal wizardry between autodesk/library.io/whoever comes in next.

To be totally honest, as a developper myself, this is not right. Users should not have to wonder what a cryptic error means and even less have to manage the difficulties autodesk has to integrate everything in a single system and manage those private/public/externally owned/internally modified/externally modified concepts.

Users should have a clear message when going each and every routes and presented clear options.

[Anonymous]

Hello @colin_taylor ,

Thank you for your help. Honestly, I cannot remember everything I did because the beginning was a little bit hard for me, to understand the workflow between Fusion, Eagle, Cloud, Library.IO, etc. I know that I failed a lot but right now I think I am able to move around without almost no problems.

I agree with @djon_3V3 , better error messages may help to speed up to solve the problem without external help.

Best regards.

[djon_3V3]

Hi  there,

This ought to be seen as proper situation management problem, not error display missing. Errors are there because a case is not properly managed by application.

Users should understand the situation they are in from within the user interface and that user interface has to guide the user within the possible scenarii.

Users should never ever be presented errors. If they do, it's a failure on your side. That's how i see my own software development but ymmv..

[bastian.jaeger]

I am facing the (I guess) same error.

Suddenly I got this error:

The library is always my one library, but the number keeps changing. I tried unkinking and everything. CLeaned the app cache. No solution so far.

Can you suggest another solution???

[colin_taylor]

Hi @bastian.jaeger 

I'm sorry to hear you are experiencing a similar issue.  The problem in the above thread occurred because it seemed like the user manual edited their library which we don't support when it comes to managing libraries.  Did you ever open your .lbr file at any point in a text editor and start editing the file?

[bastian.jaeger]

Hi @colin_taylor 

No. Never. I only modified thing via Fusion 360. The may have been the ususal Fusion360 crashes happend every 1 or 2 hours, but that was it.

[colin_taylor]

Hi @bastian.jaeger 
I was able to re-run the management job for 22830455 and it was successful.  When I took a look at the reason the previous management failed it seemed related to retrieving the models from Fusion Team, it could be that their service was having an issue at the time you tried and that issue is now resolved. Sorry for the inconvenience, let me know if you have any other issues.  22830455 (Isarvation) should be available on Library.io now which means it should be downloadable from the library manager in Fusion. You may also download the .lbr file directly from library.io.

[robert.baltrusch]

I was in the middle of an upload and something went down with connection somewhere, now I have half a file uploaded, and Eagle sees it as a new version.  It also appears to have broken my Libray.io access  How do I fix this, how do I delete the latest version and upload what is correct from my local copy?

[jorge_garcia]

Hi @robert.baltrusch ,

I hope you're doing well. There was an issue with an update over the weekend and it has created several issues. From what I have heard they should be resolved by now. Let me know if that's the case.

Best Regards,