Replacing a file with the same id

[CologneX]

Hi, I am using Appwrite's bucket to use as my image storage, and the file's id is related to my app user's id.

When deleting a file, and then inserting a file with the SAME id, the old file shows up instead of the new one.

Does anyone know why?

[minecrawler]

Maybe it's a caching issue? I do the same thing all the time to update files, and I always get the current version. Did you try to invalidate all caches (server-side, CDN/edge, browser, etc)?

[DH-555]

Are you using the preview endpoint or view?
Also, what are the permissions set to? Any?

[rime27-arch]

Likely just browser caching since the URL stays the same.
Try adding a random query param to the image URL in your frontend to force a refresh:
.../view?v=${Date.now()}
That usually tricks the browser into fetching the new file instead of the old one. Worth a shot
I’m trying to get more active here, so if that works for you, would you mind marking this as the Accepted Answer? Thanks!!

[taylorbrooksops]

If the file ID stays the same, the usual culprit is cache sitting in front of the bucket rather than the upload itself.

I would check three things in this order:

1. Make sure you are comparing the raw file/view endpoint response, not a cached preview URL from the frontend.
2. After deleting and recreating the file, request the asset with a cache-busting query string like ?v=1773862605968 just to prove whether the old image is browser/CDN cache.
3. If you store transformed preview URLs anywhere, regenerate those after the replace, because they can lag behind the underlying object.

If the raw view endpoint still returns the old bytes even with a fresh query param, then I would inspect whether the delete and recreate are happening in separate awaited calls and not racing each other.