What problem does it solve?
When a built Power Apps mobile extension (.ppmplugin) crashes, silently does nothing, or returns wrong data on device, there is no debugger or console access β only thin evidence like a PCF ErrorCode, a raw JSON diagnostic output, or a host log line. This Skill turns that limited evidence into a located root cause and a surgical fix.
Core Features & Use Cases
- Symptom-to-layer triage: Maps reported symptoms (silent no-ops, crashes at launch, error codes like PARSE or BRIDGE_FAILED) to candidate layers β PCF transport, dispatch contract, Android/iOS native modules, native load, build config, or behavior drift β using a canonical error-code catalog.
- Evidence-based diagnosis with gates: Traces the dispatch path end-to-end (PCF key β sendAsync envelope β manifest receivers β native method β response), presents a ranked diagnosis anchored to file:line evidence, and requires user approval before any edit.
- Contract-consistent fixes: Applies surgical edits that keep the committed manifest.json, native module names, and PCF composite keys synchronized, re-validating through /generate-ppmplugin-manifest when the contract moves.
- Use Case: A user reports "the button tap does nothing on Android, no error." The Skill reads the PCF index.ts, finds cordova.exec used instead of the host-injected sendAsync, diagnoses the transport bug, and applies the fix after approval.
Quick Start
Ask the agent to debug why your built .ppmplugin control shows an error code or does nothing when tapped on device.