Unable to import its own export file

[Murph4242]

"Import --mongoexport json" fails to import using both "export standard" and "export --jsonArray" exported files.

It also fails to import the file exported by MongoDB Compass using its "Export the full collection" option.

The "New Document" option also fails to create a document copied from the exported files.

There are no on-screen errors presented in any import attempt.

[rtritto]

@Murph4242 what version are you using?
On master branch both exports work with import.

[vorou]

Can repro with the docker image version 0.54.
In the browser console I see a 400 with "Bad file".

[hsiangjenli]

I've encountered the same issue while using a Docker image built with the 'latest' version.

[rtritto]

It's fixed in #996, so in versions >= 1.0.1.

@shakaran @BlackthornYugen this issue is related to the Docker Image not updated (latest version is 1.0.0-alpha).
This kind of issues should be closed as fixed or to categorize, at least, add [Docker] to title and/or create a label.

[tranduyhung]

I cloned the repository, run the development build and see this problem as well. The import response is 400, no documents are imported.

[rtritto]

I cloned the repository, run the development build and see this problem as well. The import response is 400, no documents are imported.

@tranduyhung did you import the Export --jsonArray file?

[tranduyhung]

I cloned the repository, run the development build and see this problem as well. The import response is 400, no documents are imported.

@tranduyhung did you import the Export --jsonArray file?

Yes, I tried both standard and JSON array export.

[rtritto]

Please can you write the error in logs?

[xTudoS]

Please can you write the error in logs?

I have tested in current master version and only error is when I try to import the "standard export" (see screenshot below)

Error message in my terminal:

but if I import the "jsonArray" version, it works as expected.

I don't know if it was supposed to work with both versions, but I think that a error message to tell the user what happened could be a way to solve this, once only is supported jsonArray version