Vercel blob storage doesn’t load images from two folders (error “Store not found”), neither via API nor on vercel.com when I go directly into the blob.
Re-uploading (via API and directly on vercel.com) doesn’t work.
Also no luck if I delete the folders and create them again before re-uploading.
However, uploading the same images in a different folder (both old and newly created) works perfectly fine. So does uploading new images in a different folder.
The foldernames are not using special characters or anything else beside letters (“superforecasting” and “strategyofdenail”)
I have more than enough storage and operations left.
There are no special configurations or anything unusual, about 80 other folders with images work perfectly fine.
Honestly I have no idea what could cause this weird problem. Any ideas?
Hey @raphtastisch sorry about that, did you get errors in network panel or console about your upload? What’s your store id? And any other detail will be greatly appreciated like a filename or pathname.
Hey @vvoyer!
No, there aren’t any errors in the console when I upload it.
The upload is confirmed by vercel and seems to work fine. Its just that the image can’t be opend when I use the blob url (it also doesn’t show in preview on vercel.com)
I hope this helps. Please let me know if you need any other infos:
…/stores/blob/store_pL0gS0Px1PA6SuCA/browser?directory=superforecasting
The problem is only for folders named superforecasting and strategyofdenail. All other folders are fine, even minor variations (like superforecast).
Currently I don’t have a “strategyofdenail” folder anymore since I gave them different names in my application (and thus they are created with different names in the blob) as a workaround. “superforecasting” still exists (just for reproducability reasons).
If you or any other Vercel Staff member need to look into the blob, feel free to do so, there is no data in their which aren’t publicly available anyway. But obviously don’t change anything outside of the superforecasting folder and any test folders that you create.
Thanks! @vvoyer@luimey out of curiosity:
What was the problem exactly? And is there any chance I might run into it again with other folders? (And if yes: how can i avoid that?)
Hey @raphtastisch the exact issue was that our code took your 16 charaters prefix in your file path as the store id which is incorrect. We made sure this cannot happen again, and no you won’t run into it again.
