CORS policy - Access to fetch at 'supabase.co/storage/v1'
I have two identical uploads , one is for covers and one is for avatars . Avatars works good the Covers doesn 't . The only difference from the two are the bucket name . I can not understand why I can not upload in covers . Avatars and Covers has the same Policies . How to fix this issue ? ps : Getting the upload url works , the issue is with the upload . Access to fetch at 'supabase .co /storage /v1 ' from origin ' "qqqqqqqqq -toddle .site ' has been blocked by CORS policy : No 'Access -Control -Allow -Origin ' header is present on the requested resource . If an opaque response serves your needs , set the request 's mode to 'no -cors ' to fetch the resource with CORS disabled . the issue is with the upload This shows an Auth header As well as it being selected in the dropdown That one is static If that 's not for testing purposes , then also check that I was just testing compress rates , and at some poit it refused to continue to upload . Then changed just the name of the bucket from avatars to covers and CROS . I believe is something in this case with the bucket . Can you see any issue here ? Why avatars is working and covers not ? And also the avatars stops working if changing the bucket to covers . I tried to create a new bucket and it is the same , doesn 't work . Is there a new limit for buckets in supabase for free plans ? Though , generally speaking , it is not "best practice " to create multiple buckets but rather to use folders in buckets Side thing , the auth .role ( ) = authenticated part is redundant since it is already stated in the authenticated role above that No need to have autho bearer selected in the dropdown for this call since it is not proxied You are trying to declare it twice on that call The token used should be the one returned on the signed URL request If it doesn ’t work with No Auth selected , then that ’s a clue that something is incorrect Something like bucket /avatars /userId The response @unicodes
it is empty No , you never want to use service _role client side It looks like a supabase limitation do you have a free plan ? I would like to ask if you can create a second bucket and try to upload something in the new one . Since the request one passes all the info the upload call needs You can just have one The bucket name could also be passed dynamically to the request URL call And pass in the bucket dynamically
.jpeg/public)