Unity Asset Server bug

I have some assets that cannot be removed from the "local changes" window in the asset server.

I try to "commit" and I get an error: "Empty selection"

I try to "discard" and I get an error: "Got invalid asset status from server"

I've committed other changes with no problems, but these files have sat in my window for about a week now always remaining after I commit.

Is there any way to clear these out of the window?

 

My goodness, I thought this bug was long crushed!

I haven't touched Unity since 2.1 and now that I have just upgraded to 3.1 this bug has returned its ugly face!

Unity Staff: Is there any known fix or patch available that will rectify this catastrophic Asset Server fail?
Thanks in advance, guys.


Paul W.
Director

Subspark Media
www.subspark.com

 

Has anyone found a solution to this? We have several people on our team (myself included) who are building up a list of "Local Changes" that are actually committed to the server but appear in the checkin GUI.

 

Of course just after I post this I get an idea that works (clearly a work around and not a proper solution but it helped move past this).

If you have items that are stuck in your "Local Changes" list simply rename the file and / or folder containing the file(s) and name them back.

For example, if you have a folder structure like:
-Prefabs
-->Players
-->Weapons
-->Trees
-->Particles

And you have one or more files or folders in any of the subfolders, you can rename "Prefabs" to "X", then name it back to "Prefabs" and it will clear out the ghost Local Changes for items in that folder and its subfolders.

 

Excellent, I'll have to try this. Thanks for the update.

 

Hi, Same problem, that fix did not seem to work.

I have a selection of materials and prefabs that are marked as changed locally. I have tried renaming the folder, deleting it and then discarding the delete. the same materials and prefabs become marked as changed again a little while later, eg when I close and reopen the editor but also other times.

Similar things have been happening for a while, mainly with materials, but normally the problem goes away after a few discards.

One thing I haven't tried is committing the 'changes'. Im just a bit worried that whatever is corrupt will get into the assets on the server. The persistent problem is currently only occuring on my machine (although everyone sees similar things occasionally)

 

I'm experiencing the same problem, but with an .anim file, and on Unity 3.4 (not sure what the UAS version is, but I do recall we installed it about 2 months ago). Nothing I do will make the issue go away. Even if I delete the file and commit, the "ghost change" is still there. Also, if I try to do a Compare or Compare Binary on the change, Unity Editor crashes hard.

Will there be a fix for this in the foreseeable future? There doesn't seem to be any corruption on the asset, but it's still making me jittery. If there is one part of Unity where I don't want bugs cropping up, it's the Asset Server.

 

cool solution and helps me
i though i will never find a solution and this assets will stuck here forever

 

Seeing the same on a project here.

Fix did not work here, as in our case, it involves assets that are deleted. Assets no longer in the project folder, but are marked in Local Changes as "moved"... no amount of committing, removes them from Local Changes

 

submitted, bug number is 499161

Been having this same issue for some time with an image file "stuck" in my local changes on asset server. Discarding, Commiting, and Deleting the file all do nothing. Showing history of the file shows nothing because it's a "new" file.

 

Same here with Unity 3.5.7f6

 

How are we supposed to give reproduction steps? Are we supposed to upload our repository as well? Asset Server is absolutely riddled with bugs, which have affected numerous projects I've worked on with various companies including my own. Are we really supposed to believe that no one at Unity can reproduce any of them?

 

This still has not been fixed. I see 13 files from which I get an "Empty Selection" error when I try to Commit. Just submitted a bug, #545601.

Secondly, the Bug Reporter is horrible. It always just idles at 50% done in the "Zipping <project>" status window.

 

Still broken in 4.1.2.

 

No... and that's not something I can do easily. I haven't seen a fix for this in the release notes, though, so I don't think it's been fixed.

 

This worked for me, thanks!

 

Just reproduced that issue by interruption of unity asset server services (probably got interrupted while installing IIS on server machine) and committing at the same time.
Seems like it needs some extra fail safety, something like validation.

 

Hi, after trying many alternative repos, we are finally happy with Bitbucket (online git report) and SourceTree client (Win). It works flawlessly with Unity.

 

Bit of a necro post here, but I just got this in unity 4.3.2f1.

Important bit for people who came here stuck:
Changing the affected file's folder/path name and then changing it back worked for me. (Thanks Zeruel!)
I suspect a right click -> reimport on the affected assets would do it too, but I haven't tried it.


The rest:
Full disclosure, I did not try to discard changes to verify if I got the "Got invalid asset" error result, as I didn't want to lose my work.

Seemed to be caused by interruption of service, as Naughty Leper mentioned above.

This has happened to me twice, at least once on 4.3.2f1, I'm not sure about the first time. Steps seem to go something like:

1) User starts a commit.
2) Service is interrupted by mysterious forces that hate user.
Result 1: Commit errors out. Some of the files in the commit are left in the local changes window.

3) User attempts to commit the leftover files.
Result 2: Commit starts, but errors out again. Only indication of error is a red message reading "empty selection". None of the leftover files are commited.


As for the cause of interruption in my case, I suspect either connection issues on the server side, as the internet connection can be spotty on that end for us, or "general asset server jankiness" as we have had to "try turning it off and on again" a few times over our history with the asset server.

 

Just tried re-importing the assets that were affected on my end, and that ended up solving the issue.

 

Still broken in 4.5f4

 

Not quite on topic, but I had it lose 2 commits yesterday, representing a day's work. I don't think this is safe to use at all.

 

Fixed by just creating a new project on Asset Server, breaking connection to old and restarting... cheapo forking...

 

Its now 2017 and still having this problem in 5.4.2. My fixes include renaming effected folders or doing the above as mr excessive says. Create a TEST project to connect to then connect back to your actual project then rename a folder again. This usually works for me.