You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@tima101 Noting to ourselves that in the current demo app, a user is unable to add an image to a Post due to a CORS problem.
Access to fetch at 'https://saas-api.builderbook.org/api/v1/team-member/aws/get-signed-request-for-upload-to-s3' from origin 'https://saas-app.builderbook.org' 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.
@klyburke Image upload works on YourSettings page, meaning it is not S3 problem and not cors Express middleware problem, must be problem in Post-related code. I will report here when I find out.
@tima101 Noting to ourselves that in the current demo app, a user is unable to add an image to a Post due to a CORS problem.
Access to fetch at 'https://saas-api.builderbook.org/api/v1/team-member/aws/get-signed-request-for-upload-to-s3' from origin 'https://saas-app.builderbook.org' 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.
Click to see Hill for issue #135
Click to see Hill for all issues
created by Async
The text was updated successfully, but these errors were encountered: