Open johnnyreilly opened 1 year ago
I'm having the same issue
Hi. More information would allow more accurate assistance. Generally, this happens if you didn't create a production build (npm run build), then set the app location to the output folder (e.g., dist). The timeout usually happens when you attempt to deploy your root/source folder
I also have this issue and can provide some additional context:
I successfully deployed the app the first time via an ADO Pipeline. Unlike Johnny, I pulled my site from an artifact store and published that, instead of building within the AzureStaticWebApp@0 step. Just app, no API.
With no other changes, the next time I went to deploy, it timed out as @johnnyreilly noted (effectively same screenshot). Here is my configuration, which again, worked for the first time, but fails on the second:
Azure reports the website's status as 'Failed', but won't provide any further details, so I can't determine what exactly the error is.
Despite the job saying it uploaded everything, the website itself shows the old code, so my assumption is that either the upload didn't actually happen or something else failed and Azure rolled back the files.
Update: A later deployment did succeed, so this issue seems random/intermittent
Describe the bug
Sometimes (and it is sporadic) the Azure Pipelines Static Web App task fails with the
AzureStaticWebApp@0
taskTo Reproduce Steps to reproduce the behavior:
Run a deployment that deploys the static web app in Azure Pipelines using the
AzureStaticWebApp@0
taskExpected behavior
No deployment failure
Screenshots
Additional context Add any other context about the problem here.