İçeriğe geç

Troubleshooting

Bu içerik henüz dilinizde mevcut değil.

Check the project attribute. Without a valid published project ID the element stays empty by design. Copy the ID from the project’s Share drawer.

Is the project published? Drafts are not publicly served. Publish first, or use an owner preview token for internal review.

Check the network tab for a 403. A response with error code EMBED_DOMAIN_NOT_ALLOWED means the page’s origin is not on the workspace’s domain allowlist. Note that www.example.com and example.com are different origins.

  • enterAR() must be called from a user gesture (a real click handler) — browsers may block WebXR sessions started programmatically.
  • AR must be enabled on the workspace plan.
  • On desktop there is no mobile AR — offer the QR handoff instead (Localization & AR).

The synchronous reads are caches of the last selection_change event — they are empty until the first event arrives. Gate your UI on the event: Events reference.

The part/variant keys must be the handles returned by getOptions() (the values after ?part= in share URLs) — not labels, not SKUs.

Set lang explicitly per embed instance (en, tr, ru) — the embed does not guess from the browser: Localization & AR.

Open a support ticket from the panel — include the project ID, the page URL where the embed runs, and a browser console screenshot.