Warnings regarding Photos library on macOS

Support
1

Hi,

I get these warnings whenever the backup is run.

What do they mean? And what can I do to avoid them?

Thanks in advance

Jörg

2026-05-02 17:11:52 +02 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-PathProcessingErrorIgnoreFile]: Failed to process path: /Users/XXXXXXXX/Pictures/Photos Library.photoslibrary/
ArgumentOutOfRangeException: Valid values are between -62135596800 and 253402300799, inclusive. (Parameter 'seconds')
Actual value was -62135769600.

macOS 26.4.1 (25E253)

Duplicati 2.3.0.1_stable_2026-04-24

2

Hi, same here. It started with the update to 2.3.0.0_stable and is still existing with 2.3.0.1_stable. Below 2 warnings appear 2 times each during each backup run, 1st time in an early phase of the backup and 2nd time 15 minutes later at the end of the backup:
2026-05-24 19:04:36 +02 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-PathProcessingErrorIgnoreFile]: Failed to process path: /Users/michael/Pictures/Fotos Library.photoslibrary/
ArgumentOutOfRangeException: Valid values are between -62135596800 and 253402300799, inclusive. (Parameter ‘seconds’)
Actual value was -62135769600.

2026-05-24 19:05:26 +02 - [Warning-Duplicati.Library.Main.Operation.Backup.FileEnumerationProcess-PathProcessingErrorEnumerate]: Failed to enumerate path: /Users/michael/Pictures/Fotos Library.photoslibrary/
ArgumentOutOfRangeException: Valid values are between -62135596800 and 253402300799, inclusive. (Parameter ‘seconds’)
Actual value was -62135769600.

3

PS: I found some posts when I searched for 62135769600 regarding a possible bug in the ICU time calculation, e.g. this one:

Maybe the issue came up with an update of a library used by Duplicaty, while Apple still uses the old (but wrong) value for Photos.

Regards, Michael

4

Hi @MichaelPieper, welcome to the forum.

This happens because Duplicati runs through the data twice: once for counting the files and sizes, and then for the actual backup.

The error itself happens because the value returned from Photos is outside the supported date range (in the year 0000). This has been fixed in the latest canary where we treat such a value as the lowest supported value (in the year 0001):

It will be included in the next patch stable release (2.3.0.2).