16 - Android / Flutter Troubleshooting

cd D:\MO_Project\ekyc\flutter_app\android
.\gradlew --stop
cd ..
rmdir /s /q "%USERPROFILE%\.gradle\caches\8.11.1\transforms"
rmdir /s /q "%USERPROFILE%\.gradle\caches\transforms-4"
C:\flutter\bin\flutter clean
C:\flutter\bin\flutter pub get
C:\flutter\bin\flutter build apk --release --dart-define=ENV=prod

Close the IDE fully (File → Exit, not just close the window), then nuke all Java processes.

REM See what Java processes are still alive
tasklist /v /fi "imagename eq java.exe"
tasklist /v /fi "imagename eq javaw.exe"

REM Kill them all (safe if you're not running another Java app)
taskkill /f /im java.exe
taskkill /f /im javaw.exe

REM Now the rmdir from issue #1 will succeed
rmdir /s /q "%USERPROFILE%\.gradle\caches\8.11.1\transforms"

Prevention: don't run flutter build from CLI while Android Studio is open on the same project. Pick one — either use Android Studio's built-in Build → Flutter → Build APK (reuses the running daemon), or fully close the IDE before building from CLI.

REM Is your profile actually on OneDrive?
echo %OneDrive%
echo %USERPROFILE%

If %OneDrive% points at C:\Users\...\OneDrive — yes, it's syncing. Move on to the permanent fix in issue #4. If it doesn't, the problem is Defender or AV — add exclusions (see below) and/or relocate the Gradle cache anyway.

REM 1. Create the new cache folder on a non-synced drive
mkdir D:\gradle-cache

REM 2. Set GRADLE_USER_HOME permanently (writes to user env,
REM    but does NOT update the CURRENT cmd window)
setx GRADLE_USER_HOME "D:\gradle-cache"

REM 3. Also set it for the current session so you can test immediately
set GRADLE_USER_HOME=D:\gradle-cache

REM 4. Verify
echo %GRADLE_USER_HOME%

Windows Security → Virus & threat protection → Manage settings → Exclusions → Add or remove exclusions → Add an exclusion → Folder:

• D:\gradle-cache
• D:\MO_Project\ekyc\flutter_app
• C:\flutter

cd D:\MO_Project\ekyc\flutter_app
C:\flutter\bin\flutter clean
C:\flutter\bin\flutter pub get
C:\flutter\bin\flutter build apk --release --dart-define=ENV=prod

First build takes ~8-12 minutes because Gradle re-downloads everything into the new cache. After that, builds are back to normal speed.

Edit android/app/build.gradle.kts and pin the highest version:

android {
    namespace = "com.example.ekyc_app"
    compileSdk = flutter.compileSdkVersion
    ndkVersion = "27.0.12077973"     // <- add this

    // ...
}

Make sure NDK 27 is installed (the first build will auto-download it if not — takes a few minutes):

sdkmanager "ndk;27.0.12077973"

Open android/gradle.properties and add:

# Workaround for Kotlin IC crash when pub cache and project are on
# different drives (Windows). See frontend/16-android-troubleshooting.
kotlin.incremental=false
kotlin.incremental.multiplatform=false
kotlin.incremental.js=false

This is a targeted workaround — full rebuilds are unaffected, only incremental re-compile is a tiny bit slower.

You don't fix this error directly — fix issue #1 (the transform cache problem) and this error disappears on its own. If you've done the full reset in issue #4 and it still appears, something is very wrong — check that the plugin actually exists in %PUB_CACHE%\hosted\pub.dev\, re-run flutter pub get, and check flutter doctor -v for red flags.

curl -v https://your-backend-url/api/v1/journey/init?device_type=DESKTOP

• JSON blob → backend is fine, problem is in the Flutter app
• HTML / 404 / nginx welcome → backend is wrong, fix the URL
• Connection refused / timeout → backend is down or unreachable

Edit lib/config/api_config.dart and update the URL for your target environment, or build against the correct ENV:

// Local dev
flutter build apk --release --dart-define=ENV=dev

// UAT
flutter build apk --release --dart-define=ENV=uat

// Prod
flutter build apk --release --dart-define=ENV=prod

Cross-link: See 09 - Config & Environments for the full environment flag reference.

Forward the emulator's port 5000 back to your host. The existing localhost:5000 URL in api_config.dart then just works without any code change.

REM 1. Run backend bound to all interfaces
cd D:\MO_Project\ekyc\backend\src\MO.Ekyc.Api
dotnet run --urls http://0.0.0.0:5000

REM 2. In a second cmd window: forward the port
adb devices
adb reverse tcp:5000 tcp:5000
adb reverse --list

REM 3. In a third cmd window: run the app
cd D:\MO_Project\ekyc\flutter_app
C:\flutter\bin\flutter run --dart-define=ENV=dev

The Android emulator reserves 10.0.2.2 as an alias for the host machine's loopback. Change the dev URL in api_config.dart:

case 'dev':
default:
  return 'http://10.0.2.2:5000';

Use the host machine's actual LAN IP (find with ipconfig):

case 'dev':
  return 'http://192.168.1.42:5000';   // your host LAN IP

Make sure the backend binds to 0.0.0.0 (not localhost) and that Windows Firewall allows port 5000 inbound.

For local dev, just don't build release APKs. Debug mode is faster, has hot reload, shows debug logs, and allows cleartext HTTP out of the box:

cd D:\MO_Project\ekyc\flutter_app
C:\flutter\bin\flutter run --dart-define=ENV=dev

Temporarily allow cleartext in android/app/src/main/AndroidManifest.xml:

<application
    android:label="ekyc_app"
    android:usesCleartextTraffic="true"
    android:name="${applicationName}"
    android:icon="@mipmap/ic_launcher">