Mobile Debugging
Resolve React Native debugging issues
Mobile issues can span Metro, native tooling, emulators, and application code. This skill provides structured checks and targeted commands for React Native and Expo debugging.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "Mobile Debugging" from https://skillstore.io/skills/babakbar-mobile-debugging.md and its manifest at https://skillstore.io/api/skills/babakbar-mobile-debugging/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "Mobile Debugging". Metro reports an unresolved module after a dependency update.
Expected outcome:
- Check the import path and installed dependency first.
- Stop Metro, clear the relevant cache, then reinstall dependencies only after confirming the project state.
- Restart the bundler and verify the error no longer occurs.
Using "Mobile Debugging". A React Native screen drops frames during scrolling.
Expected outcome:
- Add render-time logging to the affected component.
- Compare render duration with a 16 ms frame budget.
- Inspect subscriptions, timers, and props that can trigger unnecessary rerenders.
Using "Mobile Debugging". An Android device crash has no visible JavaScript error.
Expected outcome:
- Collect Logcat output while reproducing the crash.
- Check for Java exceptions and native module compatibility.
- Compare the failing device, build type, and recent dependency changes.
Security Audit
SafeThe skill is a React Native and Expo troubleshooting guide with no evidence of prompt injection, covert data collection, or unauthorized network activity. Several documented commands can delete caches or simulator data, alter builds, install packages, or terminate processes; users should review them before execution.
Capability review items (11)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
โ๏ธ External commands (26)
๐ Network access (3)
๐ Filesystem access (2)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/babakbar-mobile-debugging/audits/16?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/babakbar-mobile-debugging?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/babakbar-mobile-debugging?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/babakbar-mobile-debugging/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/babakbar-mobile-debugging.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
BabakBar. (2026). Mobile Debugging security audit report (audit version 16) [Author version unspecified]. Skillstore. https://skillstore.io/skills/babakbar-mobile-debugging/audits/16BibTeX citation
@techreport{babakbar-babakbar-mobile-debugging-2026,
author = {BabakBar},
title = {Mobile Debugging security audit report (audit version 16)},
institution = {Skillstore},
year = {2026},
number = {16},
url = {https://skillstore.io/skills/babakbar-mobile-debugging/audits/16},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "Mobile Debugging security audit report (audit version 16)"
version: "unspecified"
type: report
authors:
- name: "BabakBar"
date-released: "2026-07-18"
url: "https://skillstore.io/skills/babakbar-mobile-debugging/audits/16"
identifiers:
- type: other
value: "skillstore:babakbar-mobile-debugging:audit:16"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Restore a failing Metro build
Clear relevant caches and check dependencies when the bundler cannot resolve modules.
Investigate device-only crashes
Collect iOS or Android logs and compare native error details with recent changes.
Find rendering regressions
Add focused render-time logging to identify components exceeding a frame budget.
Try These Prompts
My React Native app cannot resolve a module. Give me the safest Metro troubleshooting steps and explain which commands change files.
My Android React Native build fails after adding a native module. Help me interpret the error and propose checks before cleaning build artifacts.
My Expo screen feels slow. Show how to measure render duration, identify likely rerender causes, and propose a validation plan.
Create a step-by-step plan to diagnose a crash that occurs only on Android release builds. Include logs to collect, hypotheses, and safe rollback steps.
Best Practices
- Reproduce the issue and save the full error before running cleanup commands.
- Confirm the target project, device, port, and data scope before executing destructive commands.
- Change one variable at a time and verify the result after each step.
Avoid
- Do not delete simulator data or project dependencies before collecting error details.
- Do not use forceful process termination without confirming the process and port.
- Do not treat device logs as complete evidence without checking build type and environment.