#Deployment cache errors

1 messages · Page 1 of 1 (latest)

frigid quarry
#

Follow-up: headers + repro for image upload
The app is still intermittently serving old bundles. When index.html references main.0678ca51.js, the CDN sometimes responds with main.4515fd16.js. This mismatch correlates with “Failure to upload image” on campaign submit.

Please confirm:

Full edge purge for wefundwe-crowd.emergent.host and wefundwelive.com, including index.html and Service Worker assets, not just hashed JS.

Set cache policy: index.html Cache-Control: no-store (or max-age=0, must-revalidate), hashed assets public, max-age=31536000, immutable.

Verify the upload endpoint (S3 or storage) CORS allows wefundwe-crowd.emergent.host and returns a JSON body the client expects (imageUrl or url field).

Confirm the live HTML now references and serves main.0678ca51.js (no SW injecting an old precache).

Repro (client):

Campaign form → choose JPG under 900 KB → Submit → “Failure to upload image”.

Console often shows 404/403 or CORS on the upload PUT/POST.

Please fix: ensure the latest bundle is served and that the upload route, CORS, and response schema are in sync.

knotty anvil
#

Hi, CDN cache clearling isn't neccessary on our platform. Please do not have the agent fix issues in deployment. The issue you faced is due to CORS policy and the CORS_ORIGINS was set to "*" in your Deployment panel's Env Variables section. We have replaced it with the URL of your custom domain and redeployed. It will work now.

Your uploads are being saved in code base instead of s3. There is no implementation of s3. Please have the agent replace the current upload method with s3 uploads.

solid mural
wheat pebble
#

@solid mural This is a common issue i have seen before in the community also

the reason this happens because your domain might have connect to other job

you can check and if its connected to other job then unlink from it and link it in latest job