Skip to content
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

Antd React Upload component corrupt the .xlsx file #17268

Closed
1 task
chujian-zoe opened this issue Jun 24, 2019 · 6 comments
Closed
1 task

Antd React Upload component corrupt the .xlsx file #17268

chujian-zoe opened this issue Jun 24, 2019 · 6 comments
Assignees

Comments

@chujian-zoe
Copy link

  • I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

http://ant.design/components/upload

Steps to reproduce

{this.uploadFiles(info,"xxx")}}> 上传文件

What is expected?

the .xlsx file uploaded to the linux server is not corrupted. And can be opened in Windows correctly when downloaded from the server.

What is actually happening?

the .xlsx file is corrupted and can not be opened.

Environment Info
antd 3.19.8
React 16.0.0
System Windows 10
Browser Google Chrome 75.0.3770.80

Our platform is python react antd.

@chujian-zoe
Copy link
Author

our code is:

<Upload action="/fileupload?folder=xxx" showUploadList={false} onChange={(info)=>{this.uploadFiles(info,"xxx")}}> 上传文件

and the result is:
image

@afc163
Copy link
Member

afc163 commented Jun 24, 2019

I don't think it is a antd problem.

@chujian-zoe
Copy link
Author

I've worked with the problem a couple days. The .xlsx file which is uploaded to the server is different from the original one. What can I figure out the key to the problem is the difference. May I ask what the problem you think is?

@yoyo837
Copy link
Contributor

yoyo837 commented Jun 25, 2019

Check the read and write operations of the server in each step.

@chujian-zoe
Copy link
Author

OK. Thanks.

@zombieJ
Copy link
Member

zombieJ commented Jun 25, 2019

Since it's not antd issue. We can do nothing on this. Please follow @yoyo837 's advise to check which step cause it.

@zombieJ zombieJ closed this as completed Jun 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants