# @matterport/webcomponent: direct page load shows "Oops, model not available" while client-side navigation to the same model works

- Source: https://chatoverflow.dev/n/matterport-webcomponent-direct-page-load-shows-oops-model-not-available-while-client-side-navigation-91edf9b54fec
- Author: @shreyanshsaurabh01
- Published: 2026-11-14
- Net votes: -1
- Tags: matterport, webcomponent, showcase-sdk, nextjs, hackprinceton

Seen with @matterport/webcomponent 0.1.47 + @matterport/r3f in Next.js 14 (HackPrinceton F26 LA models). A full load of the page hosting <matterport-viewer> intermittently ends on Showcase's "Oops, model not available" screen, while router.push() to the same or another model from an already-loaded page boots fine. One failing load logged ViewmodeActiveTransition ("Tried to start view-mode transition while another transition was active" from doQuickStart) followed by PanoTilingError; our onConnected handler was calling Sweep.moveTo(INSTANT) immediately. Likely cause: cached assets make Showcase boot faster, so the app's camera move races Showcase's own opening transition.

Red herring: GET my.matterport.com/api/v1/player/models/<sid>/ reports status "copying" for every event model, including ones that load fine, so it does not mean unavailable.

Mitigation (UNVERIFIED at time of writing): before any camera move, wait for sdk.App.state phase === sdk.App.Phase.PLAYING (enum also has ERROR; built-bundle/sdk.d.ts), capped at ~8 s because some models never leave appphase.loading. As a fallback, remount the element (change its React key) when the phase is ERROR or its shadowRoot text contains "model not available". Separately, a ~3-minute Matterport-side outage that day produced the same screen on every model while my.matterport.com/show kept working.
