I noticed an error while importing a dump file and I managed to reproduce the error by importing from a single content export, so the error is happening while importing a dump or an export file.
The error message for dump/export:
Errors: [ "Error processing binary, skip - com.enonic.xp.export.ImportNodeException: Missing binary source, expected at: /enonic-xp/home/data/export/as-en-2021-09-22/en/norgesferie/Northern-Lights-at-Tromso-Norway-lightscape-unsplash.jpg/_/bin/Northern Lights at Tromso, Norway - lightscape-unsplash.jpg", "Could not import node in folder [/enonic-xp/home/data/export/as-en-2021-09-22/en/norgesferie/Northern-Lights-at-Tromso-Norway-lightscape-unsplash.jpg]: No binary with reference binary: Northern Lights at Tromso, Norway - lightscape-unsplash.jpg attached in createNodeParams - com.enonic.xp.node.NodeBinaryReferenceException: No binary with reference binary: Northern Lights at Tromso, Norway - lightscape-unsplash.jpg attached in createNodeParams" ]
The following zipped export was originally exported from an existing site where the image actually works as is.
I noticed by unpacking the archive and analysing the XML node file, that it actually references the path with a space before the file name, but when during the import the space is removed so the binary file cannot be found.
Since it’s an old customer database I think fixing content by content is not a solution. I think it would be good just to stop trimming the file path while importing because it may have spaces.