[BUG]: AzureRmWebAppDeployment@4 broken after update

[JackDC16]

Task name

AzureRmWebAppDeployment@4

Task version

4.223.0

Environment type (Please select at least one enviroment where you face this issue)

• Self-Hosted
• Microsoft Hosted
• VMSS Pool
• Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Microsoft Windows Server 2022

Task log

2023-05-25T11:20:39.6058763Z ##[section]Starting: Deploy to pronet-proseal-test
2023-05-25T11:20:39.6215264Z ==============================================================================
2023-05-25T11:20:39.6215422Z Task         : Azure App Service deploy
2023-05-25T11:20:39.6215509Z Description  : Deploy to Azure App Service a web, mobile, or API app using Docker, Java, .NET, .NET Core, Node.js, PHP, Python, or Ruby
2023-05-25T11:20:39.6215689Z Version      : 4.223.0
2023-05-25T11:20:39.6215763Z Author       : Microsoft Corporation
2023-05-25T11:20:39.6215863Z Help         : https://aka.ms/azureappservicetroubleshooting
2023-05-25T11:20:39.6215962Z ==============================================================================
2023-05-25T11:20:42.4388122Z Got service connection details for Azure App Service:'pronet-proseal-test'
2023-05-25T11:20:43.7843931Z Trying to update App Service Application settings. Data: null
2023-05-25T11:20:44.1540051Z App Service Application settings are already present.
2023-05-25T11:20:44.8167326Z ##[error]TypeError: Cannot read property 'retrieveSecret' of undefined
2023-05-25T11:20:46.4497379Z Successfully added release annotation to the Application Insight : pronet-proseal-test
2023-05-25T11:20:51.4141159Z Successfully updated deployment History at https://pronet-proseal-test.scm.azurewebsites.net/api/deployments/202531685013646441
2023-05-25T11:20:51.4163759Z App Service Application URL: http://pronet-proseal-test.azurewebsites.net
2023-05-25T11:20:51.4338472Z ##[section]Finishing: Deploy to pronet-proseal-test

Relevant log output

##[error]TypeError: Cannot read property 'retrieveSecret' of undefined

Aditional info

Previous version of 4.221.103 was working, and since seeing the update to 4.223.0 I am hitting this error.

[StefH]

Same error here (on self hosted), reverting to 4.221.103 solved the problem.

[Garbageous]

We are having the same error. Also self hosted.

[ppanyukov]

There is also a breakage in JSON transform, which is very similar to the past issue #16821

Nothing gets replaced with the following warnings:

##[warning]Resource file haven't been set, can't find loc string for key: JSONvariableSubstitution

I can confirm everything was working with 4.221.103 and got broken with 4.223.0 today.

It's broken on all agents:

• Our self-hosted Linux agents
• MS Hosted ubuntu-latest
• MS Hosted windows-latest

@StefH can you share how to revert to an older version of this task?

EDIT1: We are on the classic release definitions, not yaml, and as someone else mentioned, I can't see a way to use precise version there. Just 4.*.

[nilberilkarakus]

We have the same issue with version 4.223.0 , reverting to version 4.221.103 like below helped :

- task: AzureRmWebAppDeployment@4.221.103

[enigmab17]

Same problem here, but you cannot specify/revert exact sub-version of a task to use in Release management, outside of YAML pipelines as far as I am aware. If you can please, someone tell me how!

[GerardGroenewegen]

same issue here, ##[error]TypeError: Cannot read property 'retrieveSecret' of undefined

[etheone]

Same issue here using V4 of Azure App Service Deploy. It works if we change the version of the task to V3.

[mortenengel]

Same, also created bug here: https://developercommunity.visualstudio.com/t/Azure-App-Service-deploy-failing/10375407

[AndreaCuneo]

same here. hosted agents, classic Release.

[earthcoder]

There is also a breakage in JSON transform, which is very similar to the past issue #16821

Nothing gets replaced with the following warnings:

##[warning]Resource file haven't been set, can't find loc string for key: JSONvariableSubstitution

I can confirm everything was working with 4.221.103 and got broken with 4.223.0 today.

It's broken on all agents:

• Our self-hosted Linux agents
• MS Hosted ubuntu-latest
• MS Hosted windows-latest

@StefH can you share how to revert to an older version of this task?

EDIT1: We are on the classic release definitions, not yaml, and as someone else mentioned, I can't see a way to use precise version there. Just 4.*.

@ppanyukov
We just changed to version 3 from that drop-down, everything seems ok but had to change some simple configs like slot changes

[mortenengel]

There's another open issue - seems they've reverted it for now:
#18361 (comment)

[JackDC16]

Yeah confirmed as working now in our pipeline.

[ghost]

Duplicating #18361 . A fix is applied, you should receive it soon.