Tool Library Disappears

[Anonymous]

When I create a new tool library within either Local or Cloud and create some dummy tools within the new tool library and exit from the CAM Tool Library Dialog and then reopen it, any changes I have made (in terms of libraries and tools) have disappeared. 

[ToddHarris7556]

This was a recognized issue some time back, but my understanding was that it has mostly been addressed with recent updates. I know the issues *we* were experiencing went away.

Are you using Fusion Team? Single user? Sharing cloud libraries with anyone? There were some weird issues with corrupt libraries that could be fixed by deleting local cache files.

[Anonymous · Accepted solution]

The current project is shared between two users. I have enabled cloud libraries (as that is what I hoped to use) but the issue still persists between local and cloud tool libraries. I have uninstalled fusion and ran the Fusion360 Cleaner which to my understanding should remove any local caches. Restarted the computer and install fusion. The issue still persists. 

I have also navigated to:

Windows:  %localappdata%\Autodesk\Autodesk Fusion 360\ <AlphanumericID>\W.Login\M 
Mac:  Mac HD>Users>USERNAME>Library>Application Support>Autodesk>ALPHANUMERIC ID>W.login>M 

and looked through the JSON files to see whether the data was there and just not being displayed in Fusion. There was only one .json file and the contents show there is no data present.

{
    "data": [
    ],
    "version": 1
}

Another debugging step was to try and add a new library to the Cloud dir. I entered "VF2" and confirmed the rename and the text changed back to 'New Library'. However, when I try a random alphanumeric phrase 'sdfsd2' the library name sticks, however, the issue of data being retained still persists. I add a dummy tool, close the panel and reopen the library to find the tools missing and the library gone. To me, this feels like there is a cache somewhere of library names/library data that still persists otherwise what could cause refusal of previously used library names? 

So more looking...

I found when you create a new library it gets saved to:

C:\Users\ <USERNAME> \AppData\Local\Autodesk\webdeploy\production\<AlphanumericID>

after sorting for JSON files. I found a long list of the random libraries I tried to make.

I removed all of those and started from the beginning.

Opened the tool library created a library under Cloud called 'VF2' and added multiple dummy tools and observed the VF2.json being created and the file size increasing with the addition of each tool. When looking into the file there appears to be all the appropriate data being written to the file. 

I then closed the tool library panel and reopened. The VF2 library has disappeared, the library json file still exists and the data is still the same. This is also true for the (%localappdata%\Autodesk\Autodesk Fusion 360\ <AlphanumericID>\W.Login\M ) location. For the moment I can get around this issue by right-clicking on the Cloud library and selecting import and then navigating to the location of the 'VF2.json' file but "REALLY ?!, nobody got time for that".

UPDATE -- after posting this I then closed fusion and reopened it (last ditched attempt) !! THE LIBRARY IS STILL THERE !! It seems like importing it manually after creating it did the trick. Hope this helps others. and thank you @ToddHarris7556 for your reply

[jeff.pek]

Hi all -

There is a current issue where library rename will try to write the iibrary into a different location. This could cause a few different symptoms, depending on whether that location exists or not.

This could cause a rename to appear to work, but then the original library is in place when you reopen the TL, or could cause it to seem to disappear, when it's actually being written to the other location (as noted above). If the above happens, you can manually move the library file back into the standard location, and things should be OK again.

This issue is fixed in the upcoming update.

Jeff

[ToddHarris7556]

You've done all your homework - those were all the steps that I was taking trying to get it sorted a few months back. 

It was maddening, to be sure, but it's become way more stable. Thanks to @jeff.pek and all the AD folks that jumped in to chase it down. Hopefully the last gremlins are being worked out 🙂