0.png, 0.json, 1.png, 1.json ... are all renamed with the same naming convention when uploaded to AWS.
The screenshot below showcases an example of this instance.
These are two different AWS S3 Bucket. We can see that the naming convention is the same for some assets, as they share 0.png and 0.json...
Having two collections in the same bucket would have collision and disrupt everything.
Suggestion:
When uploading to AWS, upload all under a directory ./collectionName/0.png, ./collectionName/0.json -- That way, different collections (with different names of course) can be uploaded to the same S3 bucket without collision
When uploading to AWS, simply use 0.png, 0.json as the name of the files (that is to have a consistent naming convention that can be deduced)
Issue description
0.png, 0.json, 1.png, 1.json ... are all renamed with the same naming convention when uploaded to AWS. The screenshot below showcases an example of this instance.
These are two different AWS S3 Bucket. We can see that the naming convention is the same for some assets, as they share 0.png and 0.json... Having two collections in the same bucket would have collision and disrupt everything.
Suggestion:
Relevant log output
No response
Priority this issue should have
Medium (should be fixed soon)