API: /contents returns empty when the file was created using binary

[Denny-g6labs]

ACH Version

moov/ach:v1.37.5

What were you trying to do?

I'm calling files/create with either a json or a text/plain (binary data).

1. When using JSON, all is fine.
2. When using binary data, I can't call /contents afterwards with the id, because the response content of it is empty.

As a workaround I call the (first delete and to prevent getting an already exists error) create endpoint again with the returned json structure of the first create call (using binary), so afterwards I can use /contents. While doing that I realized that the following error was raised during the second call:
Batch numbers must be in ascending order, batch 24636 is less than or equal to the previous batch: 24640.
Then I added the query parameter "allowUnorderedBatchNumbers": True (Or unorderedBatchNumbers (deprecated)).

So I see two issues:

1. Somehow the file with the generated id is not not registered properly when using binary, so I can't get the binary content back
2. The batch order is not checked at all when using binary

What did you expect to see?

Getting the binary same content when using contents after a create call with binary content.

What did you see?

An empty response of the contents call.

How can we reproduce the problem?

1. Call create API with binary file
2. Call contents with the id of the response json field (id)
3. The response content is empty but should contain the same thing as the input (1.)

[adamdecaf]

What do you mean "binary"? We don't accept raw bytes in that endpoint. The accepted formats are ASCII bytes (nacha format) or out JSON representation.

[DennyWeinberg]

I mean ASCII bytes in nacha format.