I’m getting this dialog when when every I’m checking in changes to my project. When I close the dialog the files checked in anyway, most of the time at least. Any idea why this might consistently be happening? Probably not a stuck file since it goes through regardless. Feels like a potential timing issue from the Unity end.
I’m using Unity 2022.3.3f1 and Rider 2023.1.3 and am checking in from Unity Version Control panel.
We have released a new version 2.0.7 of the Version Control package for the Unity Editor.
It will be the default version in upcoming new Unity Editor releases, but in the meantime, can you upgrade using the Package Manager?
We have released a new version 2.0.7 of the Version Control package for the Unity Editor.
It will be the default version in upcoming new Unity Editor releases, but in the meantime, can you upgrade using the Package Manager?
I have update package to 2.0.7 and the problem still persists. Restarting unity afterwards had no effect. Neither did updating rider to latest.
Hi, sorry for my mistake but the error we just fixed is not the same as you are currently reporting:
In this case, the error says ‘an existing apply local changes operation …’ instead of checkout operation, so it’s a different error but maybe the origin of the problem is something related. The error we fixed is:
An existing checkout operation has locked the workspace
Do you easily reproduce the error? What are the steps to reproduce it? If you could include a short video, we would appreciate it. We would like to check the status of the file when you are running the checkin.
Can you attach the Plastic client logs letting us know the estimated time when the error happened?
C:\Users\xxx\AppData\Local\plastic4\logs
I get a error box pretty much every time I try to check in. Now for instance I got this dialog and got denied.
When I tried again I got the same message I originally posted. This time the change was checked in regardless when I closed the box.
I have attached the logs.
time of attempt was around 14:08
I’m currently running Unity 2022.3.7f1 LTS with the 2.0.7 Version Control package.
btw. a tangent but I see a lot of file watching entries in the debug.log.txt for files in the project Library folder which should not be included in the repository. perhaps a bit over zealous with the file watching?
9205566–1284150–unityplastic.debug.log.txt (7.49 MB)
9205566–1284153–unityplastic.relevant.log.txt (1.66 MB)
We have detected an issue with the Unity editor version 2022.3.6f1 (macOS): When you edit a scene, it changes many files (materials) without meaning, they remain as changed, and then when you do a checkin, the error occurs.
Does it look similar to your scenario? Can you show us the pending changes view when you edit a scene? Are there many file changes that shouldn’t be there?
Yeah, this might fit my case. I have a 3d party asset that is procedurally messing with materials (Cozy Stylized Weather 2). Which is not great to begin with due to all the noise it generates. But regardless I would expect the VS integration to be able to deal with unchanged files. Perhaps the revert might trigger an editor update that would try to alter a file causing the lock to appear momentarily.
This is a common sight in changelists. when working in a scene using the asset.
The vendor has recommended ignoring these files in version control. Which is not an ideal solution but may well prevent this behaviors.
On that note, there is no option to revert all unchanged files in the Unity Version Control window nor in Rider integration or in the desktop client that I have noticed. Used it quit a lot when working with perforce.
These files are not just “unchanged” by they are checked-out. That’s why they appear in the “Checkin Changes” view.
I guess you are not manually checking out these files but the plugin is doing it.
Would it be possible to give some temporary access to the project to some of our engineers to try to reproduce and debug the issue?
Lets see if I can reproduce this in a project with just the asset in question and some token files to produce the issue.
I’m getting the same popup every time I enter or exit playmode and sometimes just while working in a scene. Doesn’t matter if I save the scene or not. It’s happening way more since I updated to version 2.0.7 of the version control package. I’m using Unity 2021.3.23f1
Since this bug seems to creep in to every version, could you allow us to opt in to the pop up window? Or could you make it warning in the console rather than locking the project completely?
Hi @flashframe , we are currently trying to reproduce the issue but it doesn’t seem to happen in every project.
Do you have some project we can temporarily access to reproduce the issue?
Hey, thanks for looking into it. It’s hard to share, since our project is big and under NDA.
Working today, this popup has not appeared at all. Which is great, but I’m not sure what is changing between sessions. So it doesn’t seem to happen reliably even within the same project.
I’ll keep an eye on it and see if I can work out what might be changing to cause it.
Correction - today it still pops up when pushing pending changes. Just not when entering / exiting playmode
I have a minimal project with only the where I can reproduce this issue and can give you access. How do you want to proceed?
Can you reach us at devops-vcs-support@unity3d.com?
mail sent
