-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling of Special Characters in Asset File Names Causes Build Failures #1266
Comments
Hi @fredrikburmester, thanks for the report. Just to clarify, what do you mean when you say "run the build process"? There are a bunch of steps in resolving and then bundling/serving assets and they vary across iOS/Android and between dev/prod - it'd help narrow down the problem. Also:
|
Hi @robhogan, sorry if I was unclear. After compiling the application with You can see in the image that the path to the font is not outputted properly, but I've also submitted an issue for that. But you can find the path in the code below. As you can see, the font file path is cut off right before the
|
Hi there,
I've encountered an issue with Metro where asset file names containing special characters (specifically the ampersand
&
) cause the build process to fail. An example of this is when using the font file namedLCDAT&TPhoneTimeDate.ttf
, which required renaming toLCDAT.ttf
to resolve the issue.This seems to be a parsing or handling error related to special characters in file names, which might not be adequately handled or escaped during the build process.
Steps to Reproduce:
&
) in the name, e.g.,LCDAT&TPhoneTimeDate.ttf
, in the assets directory.npx expo start
Expected Behavior:
The build process should handle file names with special characters without failing, or there should be clear documentation on file name restrictions.
Actual Behavior:
The build fails (or behaves unexpectedly), and the file must be renamed to exclude special characters for successful processing.
Is this a known limitation with Metro's file handling, or is this something that can be improved either in functionality or documentation?
Thanks for looking into this!
This issue was prompted by troubleshooting during development, where renaming the file resolved the build issues.
The text was updated successfully, but these errors were encountered: