Skip to content
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]: Latest CLI cannot run shopify theme dev with theme blocks in /blocks folder #5225

Closed
gideonb opened this issue Jan 17, 2025 · 2 comments
Labels
Type: Bug Something isn't working

Comments

@gideonb
Copy link

gideonb commented Jan 17, 2025

Expected behavior

When I run shopify theme dev on previous versions from late fall I don't have issues.

Actual behavior

When I run shopify theme dev on the latest version 3.73.2 with a theme that contains nested blocks I get an INTERNAL_SERVER_ERROR

Request ID: 06a9a5a6-8bd3-40d5-b9eb-eb5f21678e32-1737088919

Image

EDIT:
Not CLI's fault just bad schema code somehow causing a 500

@gideonb gideonb added the Type: Bug Something isn't working label Jan 17, 2025
@wisalmon
Copy link

GitHub Issues is a platform for tracking bugs. For additional assistance, please contact our support team.

You can access our dedicated support line using the following link: Click Here

Ticket ID: DN2784

Note: To start a conversation, click the live chat icon in the bottom corner of the page.

@gideonb gideonb changed the title [Bug]: Latest CLI cannot run shopify theme dev with theme blocks in /blocks folder [Bug]: ~~Latest CLI cannot run shopify theme dev with theme blocks in /blocks folder~~ Jan 17, 2025
@gideonb gideonb changed the title [Bug]: ~~Latest CLI cannot run shopify theme dev with theme blocks in /blocks folder~~ [Bug]: Latest CLI cannot run shopify theme dev with theme blocks in /blocks folder Jan 17, 2025
@gideonb
Copy link
Author

gideonb commented Jan 17, 2025

Turns out it was just bad schema code and confusing error output. Closing issue.

This was the schema issue=>fix if anyone runs into this later -- a second array in settings causes chaos.

Image

Reverting to the ruby version (3.69.4) gave me a filename and it was an easy find/fix from there. Latest version of CLI worked after fixing the issue.

Image

@gideonb gideonb closed this as completed Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants