Skip to content

Troubleshooting

Start from the symptom you can observe. Each entry points to the page that owns the current contract and remedy.

Required command values must be visible to client validation before submission. Put non-input required values in initialValues, or keep custom controls synchronized through currentValues; a value first created in onBeforeExecute arrives too late to satisfy the validity gate. Follow Building a form for the short rule and CommandDialog advanced features for custom inputs.

Yarn PnP cannot resolve rxjs from Arc React

Section titled “Yarn PnP cannot resolve rxjs from Arc React”

If you use @cratis/arc.react@22.6.2, that version imports rxjs without declaring it. A strict Yarn PnP consumer needs the version-specific packageExtensions entry and rxjs version shown in Getting started. Arc React 22.16.0 no longer needs this workaround.

Product CSS does not win over Components styles

Section titled “Product CSS does not win over Components styles”

Import the product stylesheet after the Components tokens and styles entries. Unlayered product CSS wins over the low-priority Components layers; a product that uses its own cascade layers must declare their order explicitly. See the Styling cascade contract and the mixed styling example.

A component import from the package root no longer compiles

Section titled “A component import from the package root no longer compiles”

The Components 4 package root is setup-only. Import components from explicit subpaths and use the current namespace-to-subpath mapping in Migrate from Components 3 to 4.

An adapter still renders a built-in control

Section titled “An adapter still renders a built-in control”

The public adapters implement the declared presentation slots rather than replacing every Components export. With the default rendererFallback='core', undeclared slots use the built-in implementation; rendererFallback='throw' rejects that fallback without adding adapter coverage. See Primitive adaptation: Fallback and Unsupported renderer claims.

Server rendering crashes on a browser global

Section titled “Server rendering crashes on a browser global”

Use the UI foundation capability matrix to check the server-rendering boundary for the component profile. For a custom portal container, resolve document inside overlayEnvironment.getContainer and return null when it is unavailable, as shown in Choose an overlay container.

For generated proxies, command authorization, command validation, and Arc request behavior, use Arc troubleshooting.