Troubleshooting and FAQ

Troubleshooting

Nothing appears in the dashboard.

Console: “Scene ‘…’ isn’t mapped to an app — not tracking.”

Console: “Manifest not found …”.

Decisions are recorded but the learner count is 0.

A tracker’s competency dropdown is empty or shows an unresolved id.

Data is going to the wrong environment.

The IdentificationPanel inspector says “Multi-object editing not supported.”

FAQ

Do I need a separate build per scenario? No. Link each scene to its app and add an AruvrImpactManager; a single build serves them all. See Multi-Scene Builds.

Does the SDK depend on any third-party packages? No — only Unity.

Can I track without placing components? Yes. Call AruvrTracker.Instance.Experienced(dpGuid) and Track(dpGuid, description) directly. The components are just the simplest path.

Is the API key ever in the build? No. Only the write-only runtime token ships. The API key stays in the editor.

What happens if the headset is offline during a session? Statements accumulate on disk and are sent when connectivity returns. Nothing is lost.

Can two scenarios in one build report to different programs? Yes — that is exactly what the multi-app manifest and AruvrImpactManager provide.

Where is the sign-in UI? The SDK provides the identity controller only. You build the screen and call Submit(...), or call AruvrTracker.Instance.Identify(...) directly. See Identifying Trainees.

How do I move a project from UAT to Production? Reconnect on the Production environment and re-link each scene. The endpoint baked into the build follows the environment you linked against.

What is “fast” for a decision? It is relative — faster than the median latency of all attempts on that decision point, not a fixed number of seconds. See Completion and Scoring.

Can I change a decision point after release? You can change its label, competency, and polarity, but do not change its GUID — history is keyed on it.