utf-16le files are corrupt after token replace (V6)

[petertheautomator]

We upgraded replacetokens from V4 to V6 and all UTF-16le files that are processed become corrupted.

How to replicate

• Create a Windows scheduled task and export it to xml (this xml is utf-16le by default)
• replace for the example the description with #{description}#
• run the replacetokens@v6 task
• try to import the xml in Windows scheduled task.

error in the example:

Settings:

- task: replacetokens@6
    displayName: "Replace tokens"
    inputs:
      sources: filles/task.xml
      missingVarLog: 'error'
      transforms: true
      telemetryOptout: true

[qetza]

Hi @petertheautomator, One breaking change in v6 is that the default value from addBom (previously writeBOM) is now false instead of true which is causing your issue.

With the following settings it will work:

- task: replacetokens@6
    displayName: "Replace tokens"
    inputs:
      sources: filles/task.xml
      addBOM: true
      missingVarLog: 'error'
      transforms: true
      telemetryOptout: true

[petertheautomator]

addBOM: true fixed the problem. Thanks for the quick response!