> ## Documentation Index
> Fetch the complete documentation index at: https://docs-unity.molca.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Hub for common issues — open the section that matches your product area.

Use this hub to jump to the right symptom list. **Feature docs** ([Core](/core/runtime-manager), [VR](/vr/scenario-manager), [Shared](/shared/game-manager), [DT](/dt/overview)) also end with their own **Troubleshooting** section for implementation-specific detail.

## By product area

| Page                                                   | Covers                                                                     |
| ------------------------------------------------------ | -------------------------------------------------------------------------- |
| [Core & cross-cutting](/overview/troubleshooting-core) | Bootstrap, DI, localization, theming, HTTP/data, content packages, events  |
| [VR SDK](/overview/troubleshooting-vr)                 | Session/scenario, locomotion, fade, inventory, steps, scoring, tour        |
| [Shared module](/overview/troubleshooting-shared)      | GameManager connection UX, media loading, preload gates, AuthUI vs VR auth |
| [Digital Twin SDK](/overview/troubleshooting-dt)       | Product boundaries, HTTP/token refresh, JSON mapping, POI layout           |

## Global reminders

* Confirm **which SDK** you are in: [Platforms](/overview/platforms), [Architecture](/overview/architecture).
* Prefer **`await RuntimeManager.WaitForInitialization()`** before resolving [RuntimeManager](/core/runtime-manager) services or subsystems unless a subsystem doc says otherwise.
* After changing **navigation**, keep `docs.json` in sync with new pages (see the repo **README** contributor guide).