After 2.0.8609 update the " Tools " Library does no load

[thepixelmaster]

After a few weeks I fired up the Fusion 360 and it prompted for updates. I respectfully complied ( what choice one has these days !?  insert grin face emoji ). Now my Fusion 360 is a brand new 2.0.8609 version. To kick the tires before committing to any  " hobby " work I extruded a simple geometry and took it to Manufacture department to virtually cut it. But the " tools " selection window remains blank.

There has been a few forum postings about the misplaced " Libraries.json " file in the user folder. In fact the Libraries.json file in my user folder is only 17kb  and I cannot locate any other copy of that file anywhere else on my computer ( MacOSX  10.13.6 ). There is also a suggestion for completely removing Fusion 360 and reinstalling to take care of similar problems. I'll keep that solution for last.   

[stephen.irvine]

Hi @thepixelmaster 

I'm sorry to hear you are having trouble. I'm afraid I'm not totally sure I understand the issue well enough to be able to help quite yet. Are you saying that:
A) The tool library never appears at all on screen when you attempt to open it
B) The tool library window pops up, but is completely empty
C) The tool library window pops up and you see the libraries list on the left and filters on the right, but the tool list itself in the middle has no tools in it?

In case of B or C would you mind sending us a copy of your Libraries.json file?
If A then it's possible your window has popped up on a second monitor or offscreen, and you need to use the alt+space move trick to get it back.

If it's none of the above, and you are able to, a screencast showing the problem would be helpful also.

Thanks

Stephen

[thepixelmaster]

Yes, it's the Case " B ".

after clicking on the " tool " to select a tool for operation, there is a blank MacosX Finder window titled " select tool ".

Please find attached a short screen capture. I tried to attached the Libraries.json file as requested but the file type was not supported. I opened that file in VisualStudio Code and saved a copy in text format to be able to attach it here. I hope that helps to move things forward

[stephen.irvine]

@thepixelmaster 

I'm afraid this is an issue we've not seen before, and it's not immediately obvious to us how to diagnose and fix it. We're looking into it but for the time being we want to make sure that you know that you can disable the update to the tool library and go back to using the old one so that you are not blocked by this issue:
https://knowledge.autodesk.com/support/fusion-360/troubleshooting/caas/sfdcarticles/sfdcarticles/How...

If you don't mind sending us the details of your Mac using system report that would be very helpful.

Thanks

Stephen

[thepixelmaster]

Stephen,

There has been a mention of somewhat similar issue a while back:

https://forums.autodesk.com/t5/fusion-360-support/cloud-tool-library-gone/td-p/8049933

[daniel_lyall]

@stephen.irvine  there are a few that have this problem, a few off the tians of CNC Facebook group members have said they are having problems like this.

[stephen.irvine]

@thepixelmaster 

The issues in the post you linked look like a combination of two issues, one being that the library sometimes appears off screen, and the other being issues with the JSON in the libraries themselves. I don't think (although I don't really have enough data to be sure of anything) that either of those issues is likely to be related to what you are seeing. The whole window being blank means that one of the core technologies we depend on has failed to work at all and unfortunately without the crash report it's pretty tricky to replicate the issue. I'm hoping there could be a clue in your machine specs, perhaps some specific OS version or hardware. 

@daniel_lyall 
If you know of more people having the same issue, it would be very helpful if you could link me to any posts on other sites, or encourage people to post details of there issue (and machine properties) here so that I can see if there are any common factors. It might be the best chance I have of identifying what the conditions required to replicate the problem are as we simply cannot replicate this bug internally at the moment.