[Bug]: On Deployment: Saving a file with the same name as an existing file does not invalidate cloudfront cache

[dinomut1]

Version

08c3b70(1.6.0)

Operating Systems

• macOS
• Windows
• Linux
• Android
• IOS

Browser (if applicable)

No response

What is supposed happened?

When a file is saved with the same name as an existing file, it should overwrite the file, and the url pointing to that file should now point to the newly saved file

What happened?

Saving a file with the same name as an existing file does not update the cloudfront url. This forces the user to save every file with a unique name to avoid the bug.

Steps to reproduce

1. On deployment, place a 3d model into a scene
2. Modify that model in some way, then save the changes using the model component export. Make sure to keep the file name the same
3. The model component will immediately try to reload that URL, and it will load the old file. Dragging and dropping the file will also produce the same old file

Relevant Info

90% sure this is a cloudfront cache invalidation problem. But it may be deeper problem with S3 itself