Having same issue with cli version 3.88.1
Don’t know this will help but I was re-trying this multiple times and got this error
20:58:33 │ app-preview │ ❌ Error
20:58:33 │ theme-extension │ └
[blocks/star_rating.liquid] Liquid syntax error (line 11):
Unknown tag 'schema'
──────────────────────────────────────────────────────
│ (d) Dev status │ (a) App info │ (s) Store info │ …
❌ Error updating dev preview
╭─ error ──────────────────────────────────────────────────╮
│ │
│ Failed to start dev preview. │
│ │
╰──────────────────────────────────────────────────────────╯
fatal error: all goroutines are asleep - deadlock!
goroutine 1 [chan receive]:
github.com/evanw/esbuild/internal/helpers.(*ThreadSafeWaitGr
oup).Wait(...)
github.com/evanw/esbuild/internal/helpers/waitgroup.
go:36
main.runService.func2()
github.com/evanw/esbuild/cmd/esbuild/service.go:114
+0x51
main.runService(0x1)
github.com/evanw/esbuild/cmd/esbuild/service.go:160
+0x50c
main.main()
github.com/evanw/esbuild/cmd/esbuild/main.go:252 +0x
b8b
goroutine 7 [chan receive]:
main.runService.func1()
github.com/evanw/esbuild/cmd/esbuild/service.go:98 +
0x45
created by main.runService in goroutine 1
github.com/evanw/esbuild/cmd/esbuild/service.go:97 +
0x1db
goroutine 17 [chan receive]:
main.(*serviceType).sendRequest(0xc00015a3c0, {0x9973a0, 0xc
000498390})
github.com/evanw/esbuild/cmd/esbuild/service.go:192
+0x12b
main.runService.func3()
github.com/evanw/esbuild/cmd/esbuild/service.go:125
+0x3e
created by main.runService in goroutine 1
github.com/evanw/esbuild/cmd/esbuild/service.go:122
+0x30e
LIVEARf
December 16, 2025, 5:45am
42
If you’re working on the app and not on the extension, please move the extension temporarily to a backup folder. Once this issue is fixed, we can resume work
I am also facing the same issue in Shopify CLI version 3.86.1
Etra
December 16, 2025, 6:03am
44
Yep same issue as everyone else.
pax
December 16, 2025, 6:04am
45
same here it was working fine before few hours
Same issue was working fine yesterday today idk what happened
Same here! Clearly a shopify issue, has anyone in shopify picked this up? They need to rollback whatever they changed
1 Like
We are also facing same issue , Can anyone ping here if someone found workaround till this is fixed , Or any specific version which is working fine .
We are also facing same issue, while running shopify app dev.
The CLI version is 3.88.1
1 Like
Same issue, doesn’t matter which cli version you are on
We are also having the same issue:
• bundle: [blocks/app-embed.liquid] Liquid syntax error (line 196): Unknown tag ‘schema’
hriks
December 16, 2025, 7:00am
52
Same issue, am on CLI v3.88.1.
I’m experiencing the exact same problem. I have app extension blocks in my theme extension that are throwing the same validation error:
Validation errors
• bundle: [blocks/ac-fbt-bundle.liquid] Liquid syntax error (line 21): Unknown tag 'schema'
• bundle: [blocks/ac-frequently-bought-together.liquid] Liquid syntax error (line 99): Unknown tag 'schema'
• bundle: [blocks/ac-similar-products.liquid] Liquid syntax error (line 63): Unknown tag 'schema'
• bundle: [blocks/ac-recently-viewed-products.liquid] Liquid syntax error (line 197): Unknown tag 'schema'
• bundle: [blocks/ac-top-selling-products.liquid] Liquid syntax error (line 69): Unknown tag 'schema'
• bundle: [blocks/ac_recommendation_app.liquid] Liquid syntax error (line 13): Unknown tag 'schema'
Hello everyone,
unfortunately I’ve been facing the same issue for the past three and a half hours and still haven’t found a solution. I’ve tried multiple tasks, but none of them worked.
Same happening to me in the latest 3.88.1, tried to rollback to 3.86.1 but facing the same error, maybe the validator is running on some external service?
can you explain more ? How can we solve that ?
Not solvable ATM, i tried rolling back, and multiple cli options, nothing works
I am facing the same issue all of a sudden, it was working a few hours ago.
pizza
December 16, 2025, 7:59am
61
Shopify developers in Canada might be sleeping. They will fix this tomorrow.
5 Likes
Please, fix, I have the same.
Does anybody have ideas for workarround?