`Unexpected end of JSON input` when I set this option in uppy-form: `multipleResults: false,`
See original GitHub issueHi,
uppy dashboard sends the following error message:
Unexpected end of JSON input
wen I set this option in uppy-form:
multipleResults: false,
Issue Analytics
- State:
- Created 4 years ago
- Comments:13
Top Results From Across the Web
Error : SyntaxError: Unexpected end of JSON input
Your code is trying to parse an incomplete JSON string, just the first chunk. The most common approach is to declare an array...
Read more >Unexpected end of JSON input when importing list from Excel
I am getting the error message "Unexptected end of JSON input" when importing a list with items from Excel to Teams.
Read more >Form - Uppy
Configures whether to extract metadata from the form. When set to true, the Form plugin will extract all fields from a <form> element...
Read more >uppy/CHANGELOG.md at main · transloadit/uppy · GitHub
@uppy/transloadit: fix outdated file ids and incorrect usage of files (Merlijn ... false by default (#2994 / @arturi); @uppy/form: deprecate multipleResults ...
Read more >"Unexpected End of JSON Input" Error When Uploading ...
This Tutorial helps to Solved - " Unexpected End of JSON Input " Error When Uploading YouTube ThumbnailThanks friends for watching this video ......
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 Free
Top 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
Oh, sorry for misunderstanding 😂
uppy.upload().then(result => console.log(result))
will return the resultobject
: https://uppy.io/docs/uppy/#uppy-uploaduppy.on('complete', (result) => console.log(result))
, same thing: https://uppy.io/docs/uppy/#complete@uppy/form@1.3.0
has been published with the fix to your issue! Thanks for reporting.