CLI schema sync/import issues after upgrade to 7.23 (CLI v13.13)

Support
1

I have…

  • [ X] Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
  • [ X] Used code blocks with ``` to format my code examples like JSON or logs properly.

I’m submitting a…

  • [X ] Regression (a behavior that stopped working in a new release)
  • Bug report
  • Performance issue
  • Documentation issue or request

Current behavior

I recently upgraded my self-hosted Squidex instance from 7.15 to 7.23. Before the upgrade, I followed the recommended steps:

  1. Set CONTENTS__OPTIMIZEFORSELFHOSTING=true.
  2. Set REBUILD__CONTENTS=true.
  3. Removed the rebuild variable once finished.

The UI seems to work fine, but I am encountering critical issues with the Squidex CLI when managing schemas.

Environment:

  • Squidex Server Version: 7.23
  • CLI Version: 13.13.0
  • OS: Windows (running via PowerShell)

The Issues:

  1. Schema Import failing silently:
  • I performed a sync checkout.
  • I manually added a new schema JSON file (copied from another project) into the checkout folder.
  • I ran the sync command, and although no errors were reported, the schema was not imported.
  1. Empty Schema on Update:
  • When I tried to update an existing schema using the JSON file obtained from a checkout, the CLI deleted all existing fields, leaving an empty schema structure.
  1. Workaround behavior:
  • I noticed that if I run schemas sync --schema <name>, it generates a JSON file containing the App ID, Version, and API calls (PUT, GET, etc.). If I manually fill that specific file with my fields and run the command again, the import works.

Observations:

It seems like the standard sync flow is not correctly mapping the fields during the “in” operation after the 7.23 upgrade, or there is a mismatch in how PowerShell handles the JSON encoding/structure with this specific version.

Am I missing a specific configuration for the CLI or a breaking change in the JSON schema structure for 7.23?

Environment

App Name:

  • [ X] Self hosted with docker
  • Self hosted with IIS
  • Self hosted with other version
  • Cloud version

Version: 7.23

Browser:

  • [ X] Chrome (desktop)
  • Chrome (Android)
  • Chrome (iOS)
  • Firefox
  • Safari (desktop)
  • Safari (iOS)
  • IE
  • Edge
2

I will have a look. Thanks for the report.

1 Like