newman: Unknown Encoding: latin1
- Newman Version (can be found via
newman -v
):4.4
- OS details (type, version, and architecture):Windows 10
- Are you using Newman as a library, or via the CLI? Both
- Did you encounter this recently, or has this bug always been there:Recently after updating to the latest version
- Expected behaviour: Should run the collection successfully
- Command / script used to run Newman:newman run “postman_collection.json”
- Sample collection, and auxiliary files (minus the sensitive details):
- Screenshots (if applicable):

- The issue happens only when collections is passed along with Data and/or environment file. The issue doesn’t happen with Node v10.7
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 16 (6 by maintainers)
@sneela787 I am able to reproduce this issue on Node v6.2.2.
The issue lies in the automatic file encoding detection logic which we added in
v4.4.0
. Its detectingISO-8859-1
encoding for the exported files and since Node v6.2.2 Buffer doesn’t supportlatin1
encoding (supported in Node v6.4.0+) the file load fails with this error. Howeverutf8
will work just fine in this case.