Diagnoses build and runtime failures across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers pub/Dart, Gradle/AGP, Xcode/CocoaPods, Metro, KMP source sets and iOS frameworks, crashes and deep links. Use for failing builds, app launches, stack traces or /reis-mobile:debug.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
One debugging process for every mobile stack. This file holds how to find a cause; each platform's error signatures and fixes live in its reference.
Choose by the stack and by the layer the error comes from — a Flutter or React Native build often fails inside Gradle or Xcode:
| The failure is in | Read |
|---|---|
| A Flutter app: pub, Dart compilation, generated code, widgets, runtime exceptions | references/flutter.md |
Gradle, the Android build, logcat crashes or ANRs (native Android, or the android/ folder of any app) | references/android.md |
Xcode, signing, CocoaPods, Swift packages or iOS crash logs (native iOS, or the ios/ folder of any app) | references/ios.md |
| A React Native or Expo app: Metro, native modules, JavaScript errors | references/react-native.md |
| Kotlin Multiplatform compilation, source-set or framework integration | references/kotlin-multiplatform.md |
| A deep link, App Link or Universal Link that opens the browser, the wrong screen or crashes (any stack) | references/deep-links.md |
When reis-mobile debug (or /reis-mobile:debug) ran, its area line points at the layer: gradle, manifest, proguard → Android; xcode, signing, cocoapods, spm → iOS; pub → Flutter; metro → React Native.
Build and crash logs bury the cause under cascading failures. Quote the line that starts the failure — the first error:, the What went wrong block, the top of the exception with its Caused by — not the final BUILD FAILED or the last frame. Ask for the full output when the user pasted only the end.
Most build failures after an upgrade are toolchain mismatches. Read the versions that decide the behavior — the SDK and toolchain versions (the doctor report shows them), wrapper and lock files, build scripts, deployment targets — and quote them in the diagnosis. Check compatibility against the official tables named in the reference; do not state compatibility ranges from memory.
Read-only commands can run: version checks, dependency trees, flutter doctor -v, ./gradlew --version, pod --version, xcodebuild -version. A build that only compiles can run when the user already ran it or agrees, since it takes time and writes build outputs.
Tie the cause to evidence: file:line, a version, a build setting or a log line. If two causes are plausible, say what evidence would separate them instead of picking one.
Answer with:
Do not edit files, upgrade dependencies or run commands that change the project, the caches or the machine — flutter clean, pod install, pod repo update, npx expo prebuild --clean, deleting DerivedData, ~/.gradle caches or node_modules — until the user asks you to apply the fix. Then apply it, run the verification and report the result.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Audits and fixes mobile accessibility across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including shared Compose UI and native hosts. Covers TalkBack/VoiceOver labels, roles, state, reading order, touch targets, text scaling, contrast and focus. Use for a11y audits, screen-reader bugs or accessible UI implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Builds native Android apps with the Android team's guides — Jetpack Compose UI, adaptive layouts, edge-to-edge, Compose styles, migrating XML views to Compose, Navigation 3 and predictive back; Android Gradle Plugin 9 upgrades, R8 keep rule analysis, profiling with Android Studio and Perfetto, and the Android CLI; Google Play policy compliance, Play Billing upgrades and the Engage SDK; Credential Manager restore and verified email; CameraX and Media3 Cast; App Functions and the ML Kit GenAI Prompt API; Wear OS, Android TV and display glasses. Use when writing, upgrading or auditing native Android (Kotlin) code for any of these topics, even if the user does not name the library.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and reviews mobile architecture across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers state ownership, data flow, modules, dependency boundaries, navigation, offline data and KMP shared source sets versus host apps. Use when structuring a feature, choosing state management, refactoring layers or deciding where a real class or screen belongs.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews mobile code for production bugs across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including KMP source-set and host API contracts. Covers lifecycle, concurrency, UI state and native boundaries with file:line evidence. Use for a code review, PR, project audit, quality check or /reis-mobile:review.
日本語の概要は準備中です。原文の説明を表示しています。
Detects the mobile stack of the current project (Flutter, Android, iOS, React Native, Kotlin Multiplatform), its languages and target platforms, using the reis-mobile detector. Use when you need to know which mobile stack a project uses before reviewing, debugging or changing it, or when the user asks "what stack is this project?".
日本語の概要は準備中です。原文の説明を表示しています。
Integrates and reviews Firebase across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform. Covers Auth, databases, Storage, Functions, FCM, Analytics, Crashlytics, Remote Config, App Check and KMP shared-to-platform SDK boundaries. Use for any Firebase setup, bug, security rule, emulator, configuration file or product integration.
日本語の概要は準備中です。原文の説明を表示しています。