files_get_preview says CSV is unsupported extension
See original GitHub issueHello,
We have a problem with previewing CSV format files.
The method we are using is dropbox.dropbox.Dropbox.files_get_preview
.
I remember in the past that everything was working fine, but now it throws PreviewError('unsupported_extension', None)
error.
In the documentation, I see that CSV format still should be supported.
Is it only us or anyone has the same issues?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
CSV Import Error - Unsupported File Format #7401 - GitHub
Importing CSV file when using a Windows 10 machine on any browser causes an Unsupported File Format error. Process. Log in to CartoDB...
Read more >Importing .CSV file to Moneydance - Infinite Kind Support
I have installed the CSV extension in MD. When I try to import the CSV file is says Unsupported CSV file then File...
Read more >Why will Switchvox not accept my .csv file for extension ...
If you experience an error when attempting to upload a .csv file when you are importing extensions to Switchvox, you may be having...
Read more >Why am I having issues with my CSV file? - Helpshift Support
When attempting to open a CSV file via Excel, you may see an alert stating 'Excel ... If you already edited your CSV...
Read more >6 Common CSV Import Errors and How to Fix Them - Flatfile
4. Values: Issues with data values can be a significant cause of CSV importing errors. These include unexpected data length – either too...
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
Thanks for the report! This looks like a bug on our side. We’ll look into it, and I’ll follow up here once I have an update for you.
Everything seems to work now.
Thank you!