Azure Static Web Apps deploy from Github fails

Question

Azure Static Web Apps deploy from Github fails

Hussein Ismail 1

Hello,
Our deployment from Github to SWA started failing after Oct 2. We have no clue what is causing it to fail. The failure error is shown in the attached image.

The frontend code does not include api folder shown from below.

Takahito Iwasa 4,851 Reputation points MVP Volunteer Moderator

2022-10-17T20:28:45.29+00:00

Hi, @Hussein Ismail

Can you share the content of .github/workflow/azure-staticwebapp.yml ?
Hussein Ismail 1 Reputation point

2022-10-18T14:32:29.683+00:00
ajkuma 28,136 Reputation points Microsoft Employee Moderator

2022-10-19T07:53:35.15+00:00

Thanks for the follow-up. As I understand, the issue started happening after Oct 2 without any changes from your end.

Just to clarify, do you already have BYOF attached to the static web app, and now trying to add managed function?
Make sure to set the api_location value to an empty string ("") in the workflow configuration file. (|| env.API_LOCATION)

As a side note, don't change the values for repo_token, action, and azure_static_web_apps_api_token as they're set for you by Azure Static Web Apps.

Please check: Skip building front-end app

To investigate this issue, we would need additional info about your subscription, for this I'll follow-up with you privately.
I'll leave this open for community members to share their insights.

1 answer

Your answer

Takahito Iwasa 4,851 Reputation points MVP Volunteer Moderator

2022-10-17T20:28:45.29+00:00

Hi, @Hussein Ismail

Can you share the content of .github/workflow/azure-staticwebapp.yml ?
Hussein Ismail 1 Reputation point

2022-10-18T14:32:29.683+00:00
ajkuma 28,136 Reputation points Microsoft Employee Moderator

2022-10-19T07:53:35.15+00:00

Thanks for the follow-up. As I understand, the issue started happening after Oct 2 without any changes from your end.

Just to clarify, do you already have BYOF attached to the static web app, and now trying to add managed function?
Make sure to set the api_location value to an empty string ("") in the workflow configuration file. (|| env.API_LOCATION)

As a side note, don't change the values for repo_token, action, and azure_static_web_apps_api_token as they're set for you by Azure Static Web Apps.

Please check: Skip building front-end app

To investigate this issue, we would need additional info about your subscription, for this I'll follow-up with you privately.
I'll leave this open for community members to share their insights.

Answer 1

To benefit the community, posting the discussion from our private comments.

@Hussein Ismail , as you mentioned -

"This solved the issue. Thank you very much. I had to use Azure/static-web-apps-deploy@latest instead of @v1 to make it work. But now everything is green again. Thanks. "

(edit: added above comment from HusseinIsmail)

Kindly pass this extra flag.

is_static_export: true

This is due to recent changes -Please see this announcement, which specifies to use this flag to continue using nextjs export feature
Azure Static Web Apps now supports server-side rendering for Nextjs applications #921

Nextjs support on Azure Static Web Apps | Microsoft Learn

Please let us know, I'll follow-up with you further.

Much appreciate your patience and collaboration!

--

To benefit the community find the right answers, please do mark the post which was helpful by clicking on ‘Accept Answer’ & ‘Up-Vote’.

Share via

Azure Static Web Apps deploy from Github fails

1 answer

Your answer