Getting an unexpected token error
Opened this issue · 3 comments
When I run the task I get the following error - Any idea?
2018-01-16T23:28:44.8433078Z Set workingFolder to default: D:\BuildAgent01\tasks\OwaspZapScan\2.0.3
2018-01-16T23:28:45.0776738Z ##[debug]agent.TempDirectory=undefined
2018-01-16T23:28:45.0776738Z ##[debug]agent.workFolder=D:\BuildAgent01_work
2018-01-16T23:28:45.0776738Z ##[debug]loading inputs and endpoints
2018-01-16T23:28:45.0776738Z ##[debug]loading ENDPOINT_AUTH_AA550998-0965-4F71-A3B8-4153B98233EC
2018-01-16T23:28:45.0776738Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_AA550998-0965-4F71-A3B8-4153B98233EC_ACCESSTOKEN
2018-01-16T23:28:45.0776738Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2018-01-16T23:28:45.0776738Z ##[debug]loading ENDPOINT_AUTH_SCHEME_AA550998-0965-4F71-A3B8-4153B98233EC
2018-01-16T23:28:45.0776738Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2018-01-16T23:28:45.0776738Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_EXECUTESPIDERSCAN
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_RECURSE
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_REPORTFILEDESTINATION
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_REPORTFILENAME
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_REPORTTYPE
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_TARGETURL
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_ZAPAPIKEY
2018-01-16T23:28:45.0776738Z ##[debug]loading INPUT_ZAPAPIURL
2018-01-16T23:28:45.0776738Z ##[debug]loaded 14
2018-01-16T23:28:45.0776738Z ##[debug]Agent.ProxyUrl=undefined
2018-01-16T23:28:45.0932997Z ##[debug]Agent.CAInfo=undefined
2018-01-16T23:28:45.0932997Z ##[debug]Agent.ClientCert=undefined
2018-01-16T23:28:45.4683106Z ##[debug]task result: Failed
2018-01-16T23:28:45.4683106Z ##[error]Unhandled: Unexpected token =
BalakumarChockalingam did you get a resolution to this issue? I am having the same problem.
Hi, a new version of the task (v2.0.5) is released now, Please check to see if this issue still exists. If so let me know here. Sorry for the delayed response.