Troubleshooting Skill — AI-Powered Diagnostics

When something doesn't work in Jahro, the cause is rarely obvious — it might be assembly scanning, registration lifecycle, method visibility, or build settings. The troubleshooting skill gives your AI assistant structured decision trees for every common failure mode.

What the skill does

When you describe a problem, the AI:

  1. Identifies the failure category (commands, watcher, console, snapshots, launch button)
  2. Walks a diagnostic decision tree specific to that category
  3. Asks targeted follow-up questions to narrow the root cause
  4. Provides the fix with code or configuration changes

Example prompts

"My commands aren't showing up in the Jahro console"

"The Watcher tab is empty even though I added [JahroWatch] attributes"

"Jahro console won't open on my Android build"

"Snapshot upload keeps failing"

"The launch button disappeared from my game"

Diagnostic categories

Commands not appearing

The decision tree checks, in order:

  1. Assembly scanning — is the assembly containing your commands included in Jahro's scan list? Check Tools → Jahro Settings → Assembly Selection.
  2. Registration — are instance commands registered with Jahro.RegisterObject(this) in OnEnable?
  3. Method visibility — static commands must be public static. Instance commands must be public.
  4. Lifecycle timing — is RegisterObject called before the console is opened? Commands registered after the console initializes appear on next refresh.
  5. Attribute syntax — is using JahroConsole; present? Is the attribute on the method, not the class?

Watcher not updating

  1. Registration — instance members need Jahro.RegisterObject(this). Static members don't.
  2. Tab visibility — values only poll when the Watcher tab is open. Open it and check.
  3. Type support — is the field a supported type? Unsupported types show as errors, not blank.
  4. Null references — destroyed objects with stale registrations show null errors. Check UnregisterObject in OnDisable.
  5. Property exceptions — if the getter throws, Watcher shows an error message for that entry.

Console not opening

  1. Enabled check — is Jahro enabled? Check Tools → Jahro Settings → Enable Jahro.
  2. Build type — in a non-development build, auto-disable is on by default. Check for "Jahro Console: Disabled in this build" in logs.
  3. JAHRO_DISABLE define — if set, Jahro is disabled unconditionally.
  4. Hotkey conflict — is another system consuming the ~ key? Check Jahro Settings for the configured launch key.
  5. Mobile activation — triple-tap must land on the game view, not on a UI element that consumes touch events.

Snapshots failing

  1. API key — is the key set in Jahro Settings? Validation should show your project name.
  2. Network access — does the device have internet? Streaming and upload require connectivity.
  3. Mode configuration — in Recording mode, you must manually upload. In Streaming mode, data sends automatically.
  4. Session limit — Jahro keeps 10 local sessions. Older ones roll off. Check if the session was already discarded.

Launch button missing

  1. UI settings — is the launch button enabled in Jahro Settings?
  2. Canvas sorting — Jahro's UI runs on its own canvas. If another canvas has a higher sort order and covers the screen, the button may be hidden.
  3. Safe area — on devices with notches, the button position respects safe area insets. Check if it's behind the notch.

Verification

After applying a fix:

  1. Enter Play Mode (or deploy to device if the issue is device-specific)
  2. Open the Jahro console and verify the previously broken feature works
  3. Check the Unity console for any remaining Jahro error messages

Frequently Asked Questions

Can the AI troubleshoot issues I haven't seen before? The skill covers the most common failure categories based on real user issues. For unusual problems, the AI can still reason about the issue using its knowledge of Jahro's architecture, but the diagnosis may be less structured.

What if the issue is a Jahro bug rather than a configuration problem? The decision trees help distinguish between configuration issues and actual bugs. If the AI exhausts all configuration checks and the problem persists, it'll suggest opening an issue with reproduction steps.

Does the troubleshooting skill work for web console issues? The current skill focuses on the Unity client side: in-game console, commands, watcher, and snapshots. For web console issues (team management, log viewer), check the web console documentation.

Last updated: April 2, 2026