Upload Failed When File Is In Deeply Nested Folder Structure

[Romeithius]

Initial checklist

• I understand this is a bug report and questions should be posted in the Community Forum
• I searched issues and couldn’t find anything (or linked relevant results below)

Steps to reproduce

• Create a local deeply nested folder structure (e.g. Folder ABCDEFGHIJKLMNOPQRSTUVWXYZ/Folder 123456789123456789/Folder ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789/Folder 123456789123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ/Folder 123456789123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ123456789123456789)
• Add File (e.g. WWWWWWWWWWWWWWWWWWWWWWWWWW.pdf) into Folder 123456789123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ
• Browse Folders and select the root folder of Folder ABCDEFGHIJKLMNOPQRSTUVWXYZ (even if you selected a subfolder that worked as a root, it does not work as a subfolder if the length including the root folder is too long).

If this file was uploaded as a file and not through the folder selection Uppy renames the file with ~ to reduce its length. While I don't like that it allow the upload to work. It seems the issue is due to the internal id being too long. If this is uploaded alongside other files, they work but when working with presigned urls Uppy stops the progression and results in a bad state for the "successful" files). Also the error returned by Uppy is "Unknown error".

NOTE: This file shouldn't open on Windows due to the folder length even though nothing is wrong with the file itself and if moved it works as expected.

Expected behavior

• Uppy should manage the id in a way that doesn't impact a successful upload

Actual behavior

• Uppy errors out and crashes the upload progression of all files uploaded alongside the problem file