Getting Null Reference Exception with v3.7.0

[ghost]

We are getting a null reference exceptions in all pipelines with running v3.7.0:

##[error]Unable to process command '##vso[task.setvariable variable=tokenReplacedCount;isOutput=false;issecret=false;]15' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
##[error]Value cannot be null.

[qetza]

Hi @quentinlami-e05043,
Could you share some diagnostics logs as i cannot reproduce the issue. Which version of the agent are you using?

[ghost]

Hi @quentinlami-e05043,
Could you share some diagnostics logs as i cannot reproduce the issue. Which version of the agent are you using?

See log file attached from version 3.7.0

3_Replace tokens in .config.log

[qetza]

Thanks, could you tell me:

• are you using Azure DevOps or TFS and which version?
• are you using the task in YAML, build pipeline (UI) or release pipeline?
• which agent are you using, hosted or private?
• which version of the agent are you using?

[qetza]

Hi @quentinlami-e05043,
I've published a patch version (3.7.1) rollbacking the output variables, it seems that they may be incompatibility with some TFS/Azure DevOps versions.
I will add the feature in a new major version so that users will optin for the feature.

[SanjayKumar-V23126]

are you using Azure DevOps or TFS and which version?
Answer: TFS 2017
are you using the task in YAML, build pipeline (UI) or release pipeline?
Answer: Release Pipeline
which agent are you using, hosted or private?
Answer: Private
which version of the agent are you using?
Answer: Agent.Version | 2.122.1

Here are the details if you want to reproduce the issue at your end.
We will test the release pipeline again with the rolled back version - 3.7.1.

[qetza]

Thanks @SanjayKumar-V23126, let me know if the issue is fixed with the latest version.

[SanjayKumar-V23126]

@qetza - Yes, issue is fixed in the latest task version (3.7.1).
Our Release pipelines are working fine now and thanks for quick turnaround.