debugging-capacitor

Diagnoses and resolves debugging issues in Capacitor applications across WebView and native layers.

Updated Dec 5, 2024
One-click install
npx skills add https://github.com/yeohj0710/wellnessbox --skill debugging-capacitor-yeohj0710
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-capacitor
Source: https://github.com/yeohj0710/wellnessbox/tree/main/.agents/skills/debugging-capacitor
Command: npx skills add https://github.com/yeohj0710/wellnessbox --skill debugging-capacitor-yeohj0710

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capacitor debugging often spans web and native layers, making it hard to diagnose crashes, rendering issues, and network problems.

Core Features & Use Cases

  • WebView debugging across iOS and Android
  • Native code debugging with Xcode and Android Studio
  • Crash analysis, log inspection, and crash report guidance
  • Network inspection, API call tracing, and performance observations
  • Configuration checks and common issue troubleshooting

Quick Start

Open the Capacitor app in your development environment and begin a guided debugging session to inspect WebView, native logs, and network activity.

Frequently Asked Questions about debugging-capacitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a Capacitor app that crashes between WebView and native layers?

Debug Capacitor WebView rendering issues by enabling platform-specific debuggers on iOS or Android, then inspecting WebView console logs and network activity to trace the rendering failure across web and native layers.

Can I inspect network API calls in a Capacitor iOS and Android app?

Debug Capacitor native code using Xcode for iOS and Android Studio for Android by enabling platform-specific debuggers to inspect native logs and trace issues bridging the web and native layers.

What is the best way to trace API calls and analyze crashes in Capacitor?

To inspect network API calls in a Capacitor iOS and Android app, use network inspection techniques to trace API calls, observe performance, and verify configuration settings during a guided debugging session.

Why does my Capacitor app show different results on web and native platforms?

When your Capacitor app crashes between WebView and native layers, diagnose the issue by enabling platform-specific debuggers in Xcode or Android Studio and inspecting native logs alongside WebView output to complete end-to-end troubleshooting.

Do I need Xcode and Android Studio to debug Capacitor native code?

To debug a Capacitor app showing different results on web and native platforms, inspect WebView and native logs to diagnose discrepancies, perform crash analysis, and check configurations for common troubleshooting issues.