Debugging Capacitor

What it does

This skill enables AI agents to diagnose and resolve runtime errors within Capacitor-based mobile applications. It specifically targets issues arising from the bridge between web views and native platforms, allowing agents to analyze logs and suggest fixes for crashes or unresponsive UI elements.

When to use it

• Your app is crashing on iOS or Android builds but runs fine in the development environment.
• You need to identify why a specific Capacitor plugin fails to initialize on a physical device.
• Debugging complex state mismatches between the web content and native Cordova/Android/iOS layers.

Key capabilities

• Analyzes Capacitor-specific error logs and stack traces.
• Identifies bridge communication failures between JavaScript and native code.
• Suggests configuration fixes for capacitor.config.ts or config.xml.
• Pinpoints issues related to plugin version incompatibilities.

Example prompts

• "Analyze this Capacitor crash log showing a 'Java heap space' error on Android 14 and suggest the necessary JVM arguments."
• "Why is my Capacitor app failing to load the camera plugin on iOS? The web view works, but the native interface never appears."
• "Debug a runtime error where the @capacitor/preferences plugin returns 'undefined' after an app update."

Tips & gotchas

Ensure you provide raw console output or specific error codes when asking for help, as generic descriptions often lack the context needed to pinpoint bridge issues. This skill is strictly limited to Capacitor projects; it cannot debug standard Cordova apps or pure web applications without a native wrapper.