Dynamic mobile app testing for Android and iOS: device or emulator setup, proxy and MITM, certificate trust, Frida or Objection, SSL pinning bypass, auth and session flows, runtime storage checks, deep links, IPC, WebViews, logs, and resilience verification. Use for live app runtime analysis and instrumentation.
インストール
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Dynamic mobile app testing for Android and iOS: device or emulator setup, proxy and MITM, certificate trust, Frida or Objection, SSL pinning bypass, auth and session flows, runtime storage checks, deep links, IPC, WebViews, logs, and resilience verification. Use for live app runtime analysis and instrumentation.
MOBILE DYNAMIC
Runtime testing for Android and iOS apps.
Use this when you need to observe or modify app behavior on a device, emulator, or test harness.
Core Workflow
Work in this order unless the user asks for a specific check:
Choose the test environment: real device, emulator, or simulator replacement strategy.
Establish proxy visibility and certificate trust.
Confirm whether pinning, root or jailbreak checks, or anti-hooking block analysis.
Test runtime behavior: auth, session, API calls, WebViews, deep links, IPC, local data, logs, and clipboard.
Separate resilience observations from real exploitable findings.
Keep evidence concrete: request or response, screen state, Frida hook result, or device-side artifact.
Environment Setup
Android:
prefer a rooted test device or emulator when advanced runtime inspection is needed
configure proxy and install trust material
use adb, Frida, and optional Objection for runtime hooks
iOS:
use a jailbroken device when runtime instrumentation is required
do not treat the iOS simulator as equivalent to a real device for black-box security testing
configure proxy visibility and trust material before deeper testing
Runtime Checks
Prioritize these areas:
auth and session behavior
network traffic, API hosts, and pinning bypass
deep links, app links, URL schemes, and universal links
IPC and platform interaction
WebViews and JavaScript bridges
runtime storage, keychain or keystore access patterns, logs, pasteboard or clipboard, and backups
root, jailbreak, emulator, debugger, anti-hooking, and tamper responses
