Library package update sync issues

[jr0dd]

So I have been plagued with an issue since the v.2703.1.11 update. I filed a report form the app and left comments when I did a fresh install in attempt to fix. The AI assistant suggested that I post here for visibility, because this makes the time consuming task of ECAD library management exponentially more time consuming. When creating a new component, everything goes smooth and can attach the 3D package to the footprint no problem and it saves without issue and uploads to my hub. If I have to have to edit a footprint, I'll edit the package in case it needs to be repositioned and save the package. The blue progress bar goes across the bottom of the Content Manager tab and everything looks like the library is good to go, but when I save the library it says it has to wait for uploads to finish. The upload was finished lol. After digging around I noticed that the in the packages tab, the package I just updated is greyed out with the progress wheel spinning and spinning. This will go on indefinitely. I then have to force close the library without saving, because fusion won't let you save while it thinks an upload is still going on. Any work that was done prior to editing a package is lost if it wasn't saved first, which has been infuriating. I eventually noticed that when I reopened the library in the packages tab there is an option to update the package to the latest version. SO the package is obviously syncing to the hub just fine, but it's then not providing the correct response to the app so it knows it completed uploading the change.

I am using MacOS ARM64. I have also created a new account, which creates a new hub and the issue replicates. Steps to reproduce:

1. create a library

2. import a component

3. attach a package to the footprint

4. save and close the library

5. reopen that library

6. edit any package it that library and save it

[Radwan-Almsora]

The core issue is a 3D package sync bug in Autodesk Fusion on MacOS ARM64 introduced in version v.2703.1.11. The software gets stuck in an infinite upload loop after a package edit, even though the file successfully uploads to the hub.

[j_r0dd]

Ok, so this is known then. I may have searched for the wrong terms before posting. For the most part I work around it, but there are those times that it gets forgotten about, I edit some symbols and footprints, forget about the issue and edit a package and then end up losing all the work I just did because I can no longer save. Anything I'm working on should be treated as priority and never depend on an upload to complete. That logic is broken period. 

[jorge_garcia]

Hey @j_r0dd ,

I don't think Radwan is correct here. How are you editing the 3D Package? The best workflow is to do it through the library. Don't edit the 3D model outside of the library because it can link to sync issues. I know this is confusing because you can plainly see the 3D Package and have access to it but it should not be edited outside of the library.

Let me know if there's anything else I can do for you.

Best Regards,

[j_r0dd]

I'm either double  clicking on the package under the footprint in the component tab or just double clicking on it from the packages tab. I attached a screen recording of the issue. 

[jorge_garcia]

Hi @j_r0dd ,

I hope you're doing well. The big problem is that you never click the Finish button in the 3D package editor. It is CRITICAL to hit the Finish button. If you just X out after a save it leaves that in an indeterminate state. Try it, if this solves the problem than it might be something for us to look into.

Best Regards,

[j_r0dd]

I get the same results. the finish button just seems to do a save and close of the file with one click. The hub never returns the proper response code to the app. The upload is obviously successful, but the apps just waits and waits and never receives what it needs. I started experiencing it the next day after the v.2703.1.11 update. I didn't want to lose all the library edits I made, so I left the house and when I returned a few hours later, the progress wheels were still spinning. #1 there should be a timeout function, so it doesn't hang indefinitely. #2 anything done locally should be the truth regardless, so really nothing should be synced until the library is saved. Even though the fix for the sync issue is probably a 5 second fix in the code, it reveals some flaws in the logic involved that can cause data loss. 

[Taylor.Chris]

Apologies - this is a known regression in the May release.  The fix is in the insider release now, will be resolved in the update coming July 7th

[j_r0dd]

That's good to hear! Thanks