We have a problem with our Zed running in the Spryker Cloud, that assets are no longer loaded (404 for every js/css file). Shop assets are loading just fine. The build pipeline has been running without any issues, also the deployment was successful. Our CloudWatch logs do not show any error related to the asset urls, neither for Zed nor for the Frontend service. Any recommendation where else to look at? Haven't found any S3 bucket + CloudFront that might serve assets, nor any documentation from Spryker side where assets are located in the Spryker cloud, so I assume Zed assets are served by the Frontend service as well. Locally, using the spryker docker/sdk, assets are build and accessible, so it seems like a Spryker cloud specific issue.

docker system prune -a && docker system prune --volumes && docker/sdk boot deploy.{project}-dev.yml && docker/sdk up

If you tried it with the project specific repository (don't want to disclose the project here in public), there we use

deploy-mutagen.dev.yml

on the dev branch. There we do not have those session problem at all. As the Frontend service container running on AWS is build through the pipeline on AWS, the local env and the containers on AWS are not comparable. Would be good to have a look into the Frontend service on AWS if public/Zed/assets/* exists and if not why they are build but not put inside.

U have to update also spryker-oryx-for-zed because after compiling assets under Backoffice/assets it copies the asset for backwards compatibility to Zed/assets folder

@mammoth-autumn-37948 You are a lifesaver. If we ever meet in person remind me I own you at least a cold beer 😉