Search Issue Tracker

Won't Fix

Votes

3

Found in

6000.0.47f1

6000.1.0b15

6000.2.0a9

Issue ID

UUM-103161

Regression

No

Merge conflict with "nameFileIdTable" is caused when a project is git cloned

-

How to reproduce:
1. Create a new Unity project with a 2D URP template
2. Create a new Github repository with Unity Git Ignore
3. Move the created project to your created Github repository folder
4. Move a .png file into the Assets folder of the repository
5. Open the project
6. Open Assets/Scenes/SampleScene.unity
7. Drag and drop your .png file from the Project window into the Scene window
8. Save the Scene
9. Exit the Editor
10. Publish the repository
11. Clone the repository into a new folder
12. Add the cloned project to Unity Hub
13. Open the project
14. Observe the Github Desktop

Expected results: "nameFieldTable" of the imported .png meta file is unchanged
Actual results: "nameFieldTable" of the imported .png meta file is changed

Reproducible with: 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Not reproducible with: 2022.3.61f1

Reproducible on: Windows 11 23H2
Not reproducible on: No other environment tested

  1. Resolution Note:

    Discarded for now.

Log in to vote on this issue

Comments (1)

  1. dean-cgs

    Apr 24, 2025 15:13

    I can confirm this constantly happens for my team as well.

    Whoever imports the png and submits it to our repo along with .meta file has an empty nameFileIdTable field.

    Anyone else who then pulls the change with the new .png file then has the nameFileIdTable field populated.

    This causing constant source control issues with .meta files of png files being modified.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues