-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: shopify theme dev - cors error Shopify Assets #3035
Comments
Is there any updates on this? I'm getting this on fonts and images |
Bumping this again, still having this issue. |
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. P.S. You can learn more about why we stale issues here. |
Bumping again |
Also bumping |
+1 |
1 similar comment
+1 |
Bump Bump |
+1 Happening on Firefox, doesn't happen in Chromium-based browsers |
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. P.S. You can learn more about why we stale issues here. |
Bump |
Hi all! This is on our radar as something to fix. Some users have reported using a Chromium based browser avoids the issue for now, so please give that a try if you need to get unblocked. Thanks! |
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. P.S. You can learn more about why we stale issues here. |
👋 Hey everyone, The new implementation has solved CORS issues. If you face a similar edge case we missed, please create a new issue with the Thanks again for reporting, everyone! |
Please confirm that you have:
In which of these areas are you experiencing a problem?
Theme
Expected behavior
No Cors Error?
Actual behavior
Cors Error.
Verbose output
Reproduction steps
Operating System
Windows 11
Shopify CLI version (check your project's
package.json
if you're not sure)3.50.0
Shell
Git Bash
Node version (run
node -v
if you're not sure)v18.12.1
What language and version are you using in your application?
N/A
The text was updated successfully, but these errors were encountered: