nturinski opened this issue a year ago · 0 comments
This most commonly occurs when a SWA is created/deployed via zipdeploy in the SWA CLI.