String Catalog Logo
String Catalog
Home
Docs
Common Parser Issues

// Troubleshooting

Common Parser Issues

Debugging localization parser failures — triage steps for unsupported file formats, locale mismatches, malformed xcstrings or XML, and stuck syncs.

When app localization parsing fails, the fastest path is to identify whether detection, validation, or sync logic failed.

Common Failures

  • Unsupported extension or path pattern.
  • Invalid JSON/XML structure.
  • Unknown locale that cannot be resolved to a supported language.
  • Security or structure validation failure (unsupported encoding, unsafe payloads, or malformed content).

Triage Steps

  1. Confirm file matches expected parser pattern.
  2. Validate encoding and structure.
  3. Verify locale code exists in supported language mapping.
  4. Inspect whether state transitions to NeedsReview are expected after base changes.

If Sync Appears Stuck

  • Check the latest sync activity and error details in the project UI.
  • Verify your source integration/webhook or upload flow completed successfully.
  • Re-run sync after fixing malformed file content.