Special characters in filename
See original GitHub issueWhen uploading files with special characters (e.g. à, é or ö) in the filename, an error message is raised:
Error in call to API function "files/upload": HTTP header "Dropbox-API-Arg": could not decode input as JSON
.
The dropbox desktop application handles special characters fine. Anybody knows why this isn’t working?
An example project producing the error message can be found at https://github.com/kapersoft/dropbox-sdk-js-special-characters-example
Node version: v6.6.0 Operating system: macOS Sierra 10.12.1 dropbox-sdk-js version: 2.4.0
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
File name constraints and best practices - Datto
A special character is a letter or symbol that cannot be used in file names because it is being utilized in another location...
Read more >Character Sets Used in File Names - Win32 apps
In both NTFS and FAT file systems, the special file name characters are: '\', '/', '.', '?', and '*'. On OEM code pages,...
Read more >Filename - Wikipedia
A filename or file name is a name used to uniquely identify a computer file in a directory structure. Different file systems impose...
Read more >Supported File Types and Valid File Names - Sfax
Supported characters for a file name are letters, numbers, spaces, and ( ) _ - , . *Please note file names should be...
Read more >What Special Characters do I need to avoid to successfully ...
Avoiding common illegal filename characters is essential to ensure successful archive. Naming conventions for all files in an archive are important, not only ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is fixed in v2.5.1.
Apologies for the delay. I’ll bring this up with the team again to see if we can get this moving.