Yeah, they’re just the old versions with no changes done to them.
To add more details, I think I enabled conflicts on the Android device maybe 2-3 days ago. Since then, these files seem to be have been generated over and over again. The folder is literally filled with them like below.
index.sync-conflict-20221006-130052-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-130052-D4DZUGP~20221006-204655.html
index.sync-conflict-20221006-131550-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-131550-D4DZUGP~20221006-204656.html
index.sync-conflict-20221006-133051-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-133051-D4DZUGP~20221006-204655.html
index.sync-conflict-20221006-140052-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-140052-D4DZUGP~20221006-204655.html
index.sync-conflict-20221006-151559-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-151559-D4DZUGP~20221006-204655.html
index.sync-conflict-20221006-161549-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-161549-D4DZUGP~20221006-204655.html
index.sync-conflict-20221006-163049-D4DZUGP~20221006-165121.html
index.sync-conflict-20221006-163049-D4DZUGP~20221006-204655.html
index.sync-conflict-20221006-171552-D4DZUGP~20221006-204656.html
index.sync-conflict-20221006-173052-D4DZUGP~20221006-204656.html
index.sync-conflict-20221006-181554-D4DZUGP~20221006-204656.html
index.sync-conflict-20221006-201551-D4DZUGP~20221006-211922.html
index.sync-conflict-20221006-201551-D4DZUGP~20221006-212149.html
index.sync-conflict-20221006-211553-D4DZUGP~20221006-211922.html
This is just one example, as the same conflicts have appeared for other files (and file types) as well.
Edit:
Something weird is going on here. For testing, I’ve disabled conflicts on GCXVKIG (Android) again, but the conflicted files are still being created, yet this time it’s on D4DZUGP (Windows). Again, the files themselves are edited at D4DZUGP (Windows) only, and GCXVKIG (Android) just receives the files without even opening or touching them.
The filenames contain GCXVKIG
now and are like
27de26d1eb814735ab524396c114f549.sync-conflict-20221007-113615-GCXVKIG.md
with the REST API info as below.
{
"availability": [
"7777777",
"UDPWEVD",
"XZZTDIY",
"GCXVKIG"
],
"global": {
"deleted": false,
"ignored": false,
"inodeChange": "1970-01-01T01:00:00+01:00",
"invalid": false,
"localFlags": 0,
"modified": "2023-10-07T11:36:17.7088374+02:00",
"modifiedBy": "D4DZUGP",
"mustRescan": false,
"name": "27de26d1eb814735ab524396c114f549.sync-conflict-20221007-113615-GCXVKIG.md",
"noPermissions": true,
"numBlocks": 1,
"platform": {
"unix": null,
"windows": null,
"linux": null,
"darwin": null,
"freebsd": null,
"netbsd": null
},
"sequence": 63522,
"size": 746,
"type": "FILE_INFO_TYPE_FILE",
"version": [
"D4DZUGP:1665135385",
"UDPWEVD:1665135376"
]
},
"globalVersions": "{{Version:{[{D4DZUGP 1665135385} {UDPWEVD 1665135376}]}, Deleted:false, Devices:{7777777, UDPWEVD, XZZTDIY, GCXVKIG}, Invalid:{}}}",
"local": {
"deleted": false,
"ignored": false,
"inodeChange": "1970-01-01T01:00:00+01:00",
"invalid": false,
"localFlags": 0,
"modified": "2023-10-07T11:36:17.7088374+02:00",
"modifiedBy": "D4DZUGP",
"mustRescan": false,
"name": "27de26d1eb814735ab524396c114f549.sync-conflict-20221007-113615-GCXVKIG.md",
"noPermissions": true,
"numBlocks": 1,
"platform": {
"unix": null,
"windows": null,
"linux": null,
"darwin": null,
"freebsd": null,
"netbsd": null
},
"sequence": 63522,
"size": 746,
"type": "FILE_INFO_TYPE_FILE",
"version": [
"D4DZUGP:1665135385",
"UDPWEVD:1665135376"
]
},
"mtime": {
"err": null,
"value": {
"real": "0001-01-01T00:00:00Z",
"virtual": "0001-01-01T00:00:00Z"
}
}
}
It seems that I’d have to disable conflicts on both sides to prevent them from being created.