"assets maps out of sync - repairing"

Hi guys,

Since I'm using Tilemaps (and prefab them) I have this warning when editor gets initialized :
"Timestamps (3763) and assets (3762) maps out of sync - repairing..."

and then

"The AssetDatabase contains a timestamp for 'Assets/Prefabs/Level Elements/Grid_Extérieur.prefab', which already has a timestamp identified as 'Assets/Prefabs/Level Elements/Grid_Extérieur.prefab' associated with it. This timestamp will be removed from the database."

Any idea on what' going on here ?

 

Are you using beta version by chance? I upgraded from 2018.2.06b to 07b and got about 70 or so error like these:

Timestamps (1679) and assets (1611) maps out of sync - repairing...
The AssetDatabase contains a timestamp for 'C:/Program Files/Unity/Hub/Editor/2018.2.0b7/Editor/Data/UnityExtensions/Unity/VR/Android/gvr.aar', but no mapped GUID. This timestamp will be removed from the database.

 

Nope I'm still running 2017.3 :/

 

It's been a month later, any updates for solutions on this?

Now on 2018.2, and my assets were created in 2018.1. No beta editors at all in between, and the assets are left untouched for 3 months. (Thanks, time...)


EDIT: Oh, found the solution. Just open the offending project. Clear all warnings about "The AssetDatabase contains a timestamp, "path/to/X", but no X" messages in the Console, then "Save Project", and finally, reopen the same project in the same editor.

 

Got the same warning! And mine was come up when I call the

AssetDatabase.CopyAsset(oldasset, newasset);

This warning is not a stable-reproduce warning, but it can cause the copying interrupt!
I don't know how to fix it, but find a replacement, that is:

Code (CSharp):

1. FileUtil.CopyFileOrDirectory(oldAssetFolder, newAssetFolder);
2. // After copy of the former line,
3. // the asset files will have same guid and file id with the original ones,
4. // so we should delete metafiles here
5. RemoveMetaFiles(newAssetFolder);
6. // Let unity reimport copied files
7. AssetDatabase.Refresh();

In my case, this replacement has never triggerred the out of sync warnings.

 

Obrigado amigo, aparentemente limpando o console, salvando e reabrindo o projeto resolveu o problema, mas mesmo que ele volte, obrigado pela sua contribuição!