Different video editing applications (non-linear editors or NLEs) read the start timecode differently in media files and this can cause issues with relink and multicam sync. I know, it's insane.
But here we are.
Good news: Eddie handles this.
If you manually downloaded the FCPXML / XML and manually imported it into Resolve (for example) and are having issues, use the Eddie extension for Resolve.
The Eddie extension for Resolve seamlessly identifies the NLE-timecode differences and adjusts for this issue.
You can also manually adjust the start timecode in Eddie to match that of the start timecode in your video editing app.
====
The most common scenario for this issue is:
customer imports the files from their local drive (instead of from Resolve)
Eddie reads the start timecode
If customer used Resolve to import clips from the bin to Eddie, Resolve specifies the start timecode instead
Then customer edits in Eddie and exports to Resolve by downloading the FCPXML from Eddie and manually importing it into Resolve.
There are issues in Resolve as start timecodes don't match.
Instead: if customer uses the Eddie extension for Resolve, the extension would identify the start timecode mismatch and adjust for it.
Alternatively: customer can manually update the start timecode in Eddie to that of the start timecode in Resolve.