Asset Server: Upgrade to Unity 4.6.x completely destroys updates/commits and local changes list!

After upgrading from 4.5.5 to 4.6.0 (or 4.6.1), tons of old revisions re-appear in the "Update" window. If you don't have any local changes (which is generally never the case in a normal working environment!), you can just hit "Update", Unity does essentially nothing (visibly), and then everything is clean again.

However - if you have local changes, some or all of these changes appear as conflicts when trying to Update. So what to do? "Skip" does not help. "Discard My Changes" is not what you want, as it would erase all your local changes. The only way to go is "Ignore Server Changes" - but this has two major caveats:
- first, if that project was not up-to-date BEFORE opening it for the first time in 4.6, you would "lose" all these server changes, as you would ignore those updates.
- and secondly, while this approach does cleanup the "Update" window - all your local changes (except the "NEW" entries) now permanently vanished from your Commit list! This is an ancient Unity bug, and the only way to make your local files (that DO differ from the server version!) reappear in the Commit list is to reimport them. As there is no way of knowing WHICH files are actually changed locally, your only option is to REIMPORT ALL ASSETS. Well, we have about 6 active projects ranging from 0.5 to 10GB, often with several local copies (i.e., for various platforms), and we have 7 people with Pro licenses in our team. Reimporting all assets in all local project instances will take about 1.5 full work days (unless you happen to have an SSD, which will reduce that time to maybe 0.5 work days), so upgrading to 4.6 will cost us about 10 man-days of busy-waiting where we effectively cannot work on our projects!

=======================================
I strongly suggest that everybody working with the Unity Asset Server does NOT try to upgrade to 4.6 until these issues are resolved!
=======================================


Is there maybe some workaround or trick besides a "Reimport All" that fixes this? It's probably merely some flag that gets incorrectly erased, as the files itself are not changed, only the status of whether a file is current or not.

 

I have a similar same problem : with 4.6.1, when working with other guys, local changes don't appear in the list, therefore I can't commit my changes. Very annoying. Like to say, impossible to work

I had to downgrade to 4.6.0, to be able to commit and update without issues.

Anyone else having problems with asset server and 4.6.1 ?

Do I need to upgrade asset server ? Sounds not a good idea...

Help from Unity Team would be appreciated, especially because I'll need to upgrade soon to 4.6.1 to have 64 bit support.

 

@Le Lag : Try right-clicking in your project tab and "Reimport All". Then go get a coffee, or go to lunch, this will take a while...
However, it should cleanup all/most problems with your commit list.

 

Can we have an official statement on this please? Unity 4.6.2 still breaks things when coming from 4.5, it is not possible for our team to upgrade, unless we are willing to invest two persondays of manual work!

Bug #651514 (opened 27.11.2014!!) which I submitted about this is still untouched...

 

@Graham Dunnett thank you for your response!

 

I've seen this occasionally happen before without any update at all, back when we used Asset Server, so it may not be related at all to the update to 4.6. It could just be a "random" Asset Server bug.