Compatibility Issues with iOS Earlier than 15: Invalid Character #

[abedshamia]

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)

Link to runnable example

No response

Steps to reproduce

1. Use Uppy in a project.
2. Attempt to run the app in a browser on iOS 14 or earlier.
3. Observe the error indicating an “invalid character #.”

This issue seems to stem from the use of private fields in the @uppy/* packages, which are not supported by these older iOS versions.

Private fields were introduced in newer JavaScript standards and are unsupported in iOS 14/13 and earlier environments. For reference:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_properties

Expected behavior

• The app should function normally on iOS 14 and relatively recent releases

Actual behavior

• The app fails to load and throws an error about the “invalid character #.”

Would you consider addressing this compatibility issue? iOS 14 and 13 are still relatively recent versions, and supporting them would help ensure broader compatibility for our users. Or if there is a workaround for it I would appreciate that!

[Murderlon]

We heavily depend on private properties/methods so I don't see us going back.

From the readme:

We aim to support recent versions of Chrome, Firefox, and Safari.

I'm afraid you'll have to use babel to transpile your code.