UVC Duplicated child error

Unity Services
,
1

Dear UVC Team,

I am getting the error message shown below whenever I want to push a new folder with files inside of it.
This happens in every workspace I download. I have updated UVC several times to the newest version, nothing has changed.

Can’t add an entry with the same name. Duplicated child [SomeName.txt].
Parent [SomeName]

My workaround is to push every folder without the files first, afterwards I can push the files without a problem. (which is a hassle)

Kind regards
Arne

1 Like
2

I dont know if this is related, but I also receive error messages like this from time to time:

image
image527×155 6.35 KB

3

Trying to check in a new folder with a new file resulted in the following new error message today:

image
image528×154 5.38 KB

4

This is the error I usually get, and also got right after the wrong header message: (I can only add 1 image per post since I am a new user)

image
image529×155 5.97 KB

5

I got this error just now by checking in some changes, but everything was processed just fine. (I had to Refresh the Workspace though for changes to be shown)

image
image526×154 6.15 KB

6

Thank you for reaching out, and I appreciate the detailed description of the issue.

The error message you’re encountering, “Can’t add an entry with the same name. Duplicated child [file],” typically indicates that Unity Version Control (UVC) detects conflicting file entries, likely due to cached metadata or pre-existing entries in the repository.

Here’s a quick rundown of steps that may help resolve this issue:

  1. Clear Cache: Ensure there’s no cached metadata by going to your workspace settings and clearing the cache. This can sometimes resolve conflicts in file recognition.
  2. Verify File Naming: Confirm that there are no accidental hidden duplicates or similar files (like [SomeName.txt] and [SomeName.TXT]), as minor variations in file names can sometimes cause issues with version control.

If the previous steps won’t help, and Since this issue is not common and seems to be a corner case, I would prefer to review it in detail, please open a support ticket with us at devops-vcs-support@unity3d.com and forward the client logs located in:
Windows path: %localappdata%\plastic4\logs\
Mac/Linux path: $HOME/.plastic4/logs/
Also please share any hidden_changes.conf, ignore.conf and cloaked.conf you may be using.

1 Like
7

Deleting the plastic4 folder in $USER\AppData\Local\ resolved the error.
Thank you for your help @Rafafor_unity

1 Like
8

Hello, I experienced the same error, but it seems it raises only when using “view as tree visualization” option for “pending changes options”

9

@gio-pro what is your Plastic server and client version? If you upgrade to the latest version, does the issue persist?

10

I’m using Rel 11.0.16.9039 on PlasticCloud. The issue persists with the CS tree visualization.
Thank you

11

Could you open a ticket with us via devops-vcs-support@unity3d.com and forward the client logs located at:
Windows path: %localappdata%\plastic4\logs\
Mac/Linux path: $HOME/.plastic4/logs/
Also please share any hidden_changes.conf, ignore.conf and cloaked.conf you may be using.

12

I just tested the tree visualization on an Ubuntu 24 pc.
It worked fine without tree visualization, but the same error occurred with tree visualization enabled.
Disabling tree visualization resolves the error. (Pending Changes → Options → Visualization → View as a tree)