newman: Unknown Encoding: latin1

  1. Newman Version (can be found via newman -v):4.4
  2. OS details (type, version, and architecture):Windows 10
  3. Are you using Newman as a library, or via the CLI? Both
  4. Did you encounter this recently, or has this bug always been there:Recently after updating to the latest version
  5. Expected behaviour: Should run the collection successfully
  6. Command / script used to run Newman:newman run “postman_collection.json”
  7. Sample collection, and auxiliary files (minus the sensitive details):
  8. Screenshots (if applicable): image
  9. 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)

Most upvoted comments

@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 detecting ISO-8859-1 encoding for the exported files and since Node v6.2.2 Buffer doesn’t support latin1 encoding (supported in Node v6.4.0+) the file load fails with this error. However utf8 will work just fine in this case.