We're unable to validate or deploy our SuiteApp project via SDF due to a persistent "Tag mismatch!" error from server-side validation. The error provides no indication of which object or file is causing it, making it impossible to fix.
Environment
- SDK Version: 2025.2.1 (CLI jar + VS Code extension)
- Project type: SuiteApp
- Project size: 2,298 custom objects in Object folder (included zip)
Error
The error only occurs on server-side validation. The CLI's client-side validation hangs indefinitely (even with -Xss10m stack size). The VS Code extension output panel shows only "Tag mismatch!" repeated, with no preceding context about which object was being processed.
What we've ruled out
- Not a connectivity issue —
listobjects works fine, TLS handshake completes (TLSv1.3, valid DigiCert certificate) - Not specific to one account
- Not FileCabinet or Translations — error persists with both removed
- Not basic XML well-formedness — all 2,298 XML files pass
xmllint
Isolation testing results
By incrementally adding object categories back to an empty Objects, we identified which categories pass and which trigger the error:
Passing categories (1,042 objects total):
Category | Count |
|---|
customrecord (custom record types) | 444 |
customsearch (saved searches) | 277 |
custbody (custom body fields) | 88 |
custcol (custom column fields) | 131 |
custentity (custom entity fields) | 82 |
custtab (custom tabs) | 20 |
Failing categories — each one triggers "Tag mismatch" when added individually:
Category | Count |
|---|
customlist (custom lists) | 250 |
customscript (script deployments) | 603 |
custevent (custom events / script triggers) | 37 |
custitem (custom item fields) | 77 |
custrecord (custom record instances) | 27 |
customrole (custom roles) | 8 |
What we need
A way to get per-object validation errors from the server. The generic "Tag mismatch!" with no file context makes it impossible to identify and fix which specific objects are problematic. Even a log of which object the server was processing when the error occurred would be sufficient.
NetSuite support says it's not their problem and we should use this community to solve the issue.