mobile-debug
/mobile-debug
Diagnozuje błędy kompilacji i uruchamiania w Flutterze, natywnym Androidzie, iOS, React Native i KMP.
- Autor
- wrsilva ↗
- Repozytorium
- reis-mobile ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 17
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Diagnozuje błędy kompilacji i uruchamiania w Flutterze, natywnym Androidzie, iOS, React Native i KMP.
Oryginalny opis (EN)
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.
Jak działa
- 1. Pick the reference
- 2. Find the first real error
- 3. Collect versions before theorizing
- 4. Reproduce safely
- 5. Confirm the cause
- 6. Propose, then wait
Podgląd SKILL.md
--- name: mobile-debug description: 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. intents: [debug, build, dependency, migration] stacks: ["*"] --- # 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. ## 1. Pick the 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](references/flutter.md) | | Gradle, the Android build, logcat crashes or ANRs (native Android, or the `android/` folder of any app) | [references/android.md](references/android.md) | | Xcode, signing, CocoaPods, Swift packages or iOS crash logs (native iOS, or the `ios/` folder of any app) | [references/ios.md](references/ios.md) | | A React Native or Expo app: Metro, native modules, JavaScript errors | [references/react-native.md](references/react-native.md) | | Kotlin Multiplatform compilation, source-set or framework integration | [references/kotlin-multiplatform.md](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](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. ## 2. Find the first real error 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. ## 3. Collect versions before theorizing 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. ## 4. Reproduce safely 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. ## 5. Confirm the cause 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. ## 6. Propose, then wait Answer with: - **Cause** — one or two sentences, with the evidence. - **Fix** — the minimal change, as a diff or exact commands, in order. - **Side effects** — what else the fix changes: a higher minimum Android or iOS version, a Gradle or Kotlin upgrade that CI needs too, pods changing version. - **Verify** — the command that failed, run again. 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.
Pliki w paczce (17)
- SKILL.md 4 KB
- references/android.md 3 KB
- references/deep-links.md 5 KB
- references/flutter.md 2 KB
- references/ios.md 2 KB
- references/kotlin-multiplatform.md 1 KB
- references/react-native.md 4 KB
- references/android/anr.md 5 KB
- references/android/gradle-build.md 7 KB
- references/android/memory-leaks.md 3 KB
- references/flutter/build.md 5 KB
- references/flutter/errors.md 3 KB
- references/flutter/layout-issues.md 5 KB
- references/flutter/package-conflicts.md 5 KB
- references/flutter/runtime-errors.md 6 KB
- references/ios/cocoapods.md 5 KB
- references/ios/xcode-build.md 6 KB
Wersje
W bazie nie ma innych skilli o nazwie mobile-debug.
Migawka bazy z 13.11.2026 · wersja paczki 4c26afcca55d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100mobile-code-review
Recenzuje kod mobilny pod kątem błędów produkcyjnych we Flutter, natywnym Androidzie i iOS, React Native oraz Kotlin Multiplatform: cykl życia, współbieżność, stan interfejsu i granice natywne, z dowodami file:line. - 100mobile-architecture
Projektuje i recenzuje architekturę mobilną we Flutter, natywnym Androidzie i iOS, React Native oraz Kotlin Multiplatform: własność stanu, przepływ danych, moduły, nawigację i dane offline. - 100mobile-dev
Buduje, uruchamia i debuguje aplikacje mobilne w Expo, React Native, Flutter oraz natywnym Androidzie i iOS: rozpoznaje stos, sprawdza toolchain, uruchamia packager i naprawia błędy buildu. - 100mobile-dev
Wspiera tworzenie aplikacji mobilnych na iOS, Androida i React Native: budowa aplikacji i ekranów, debugowanie buildów iOS oraz optymalizacja wydajności Androida. - 90mobile-kotlin-multiplatform
Buduje aplikacje Kotlin Multiplatform ze wspólną logiką biznesową i interfejsem Compose Multiplatform. - 100kmp-build-setup
Konfiguruje build Gradle dla Kotlin Multiplatform: DSL kotlin, targety (Android, iOS, JVM, JS, wasmJs), hierarchię source setów, zależności per source set, wersje pluginów i konfigurację Androida.