Hi - cannot build deployment because of above error, but the actual offending path is not listed in the log it just says The following destination path is too long: and nothing else. Wondering if the One Drive path names are breaking some sort of limitation?
I remember getting the same issue a few months ago. This answer talks about something very similar. TestStand Deployments and Packed Libraries have this in common, you need to be mindful and force some of your files to sit at specific paths to avoid things getting out of hands.
@RaviShrigiri's answer will definitely be a possible solution, you just need to be mindful about the paths on the target machine.