Clean and Rebuild Cordova

—

### ✅ **1. Clean the Android build**

cordova clean android

This removes the `platforms/android/app/build` directory and resets the Gradle state.

—

### ✅ **2. Rebuild the Android platform**

cordova build android

This will:

– Reinstall Gradle dependencies
– Build the `.apk` or `.aab` in `platforms/android/app/build/outputs`

—

### 💡 **Optional: Remove and Re-add Android Platform** (if clean doesn't resolve issues)

cordova platform rm android
cordova platform add android
cordova build android

—

Let me know if you're using Android Studio or facing a specific error — I can help troubleshoot that too.

BUILD SUCCESSFUL in 949ms
1 actionable task: 1 up-to-date
Subproject Path: CordovaLib
Subproject Path: app
> Task :app:processDebugResources FAILED

> Task :CordovaLib:compileDebugJavaWithJavac
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

[Incubating] Problems report is available at: file:///home/admin1/nethues-projects/Klassenergy-project/apache-cordova/circusscanner/platforms/android/build/reports/problems/problems-report.html

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:processDebugResources'.
> A failure occurred while executing com.android.build.gradle.internal.res.LinkApplicationAndroidResourcesTask$TaskAction
> Android resource linking failed
ERROR: /home/admin1/nethues-projects/Klassenergy-project/apache-cordova/circusscanner/platforms/android/app/src/main/AndroidManifest.xml:5:5-21:19: AAPT: error: resource mipmap/ic_launcher (aka com.circusvegasonwheels.scanner:mipmap/ic_launcher) not found.

* Try:
> Run with –stacktrace option to get the stack trace.
> Run with –info or –debug option to get more log output.
> Run with –scan to get full insights.
> Get more help at https://help.gradle.org.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '–warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

BUILD FAILED in 6s
27 actionable tasks: 27 executed
Command failed with exit code 1: /home/admin1/nethues-projects/Klassenergy-project/apache-cordova/circusscanner/platforms/android/tools/gradlew cdvBuildDebug

AAPT: error: resource mipmap/ic_launcher not found.

### 🔴 Problem
Your Cordova Android build is failing because the launcher icon (`mipmap/ic_launcher`) is missing from your project’s `res` folder.

—

### ✅ Fix: Restore or Add Missing Launcher Icons

#### 📁 Path to Check:
`platforms/android/app/src/main/res/mipmap-*`

You should have at least the following files:

mipmap-hdpi/ic_launcher.png
mipmap-mdpi/ic_launcher.png
mipmap-xhdpi/ic_launcher.png
mipmap-xxhdpi/ic_launcher.png
mipmap-xxxhdpi/ic_launcher.png

—

### 🛠 Option 1: Re-generate with Cordova
If these are missing, regenerate them:

cordova platform rm android
cordova platform add android

This often restores default icons.

—

### 🛠 Option 2: Manually Add Icons

1. Add launcher icons (from another project or Android asset generator).
2. Make sure they are named exactly: `ic_launcher.png`
3. Place them under the correct directories:

platforms/android/app/src/main/res/mipmap-mdpi/ic_launcher.png
   platforms/android/app/src/main/res/mipmap-hdpi/ic_launcher.png
   ...

—

### ⚠️ Optional: Set Custom Icon in `config.xml`

If you have a custom icon, ensure it's defined in your `config.xml` like this:

<platform name="android">
    <icon src="res/icon/android/icon.png" density="mdpi"/>
    <icon src="res/icon/android/icon-hdpi.png" density="hdpi"/>
    <icon src="res/icon/android/icon-xhdpi.png" density="xhdpi"/>
    <icon src="res/icon/android/icon-xxhdpi.png" density="xxhdpi"/>
    <icon src="res/icon/android/icon-xxxhdpi.png" density="xxxhdpi"/>
</platform>

Then run:

cordova prepare android
cordova build android

—

Let me know if you want a set of default icons or a tool link to generate them.

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.

You can use '–warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.

### 🔍 Summary of the Situation

You have **two separate concerns** in your Cordova Android build:

—

## ✅ 1. **Launcher Icon Missing (Actual Build Error)**

You're still facing this **critical build failure**:

error: resource mipmap/ic_launcher not found

This needs to be fixed **before anything else**. You can:
– **Regenerate Android platform**:

cordova platform rm android
  cordova platform add android
  cordova build android

– Or manually ensure the following folder exists and contains the correct PNG files:

platforms/android/app/src/main/res/mipmap-mdpi/ic_launcher.png
  (and for other mipmap sizes too)

If it's still missing, let me know—I’ll provide ready-to-use icon files.

—

## ⚠️ 2. **Gradle Deprecation Warnings (Not Breaking the Build Yet)**

The message:

Deprecated Gradle features were used... incompatible with Gradle 9.0

Means your current Gradle (probably 8.1–8.3) is using features that will **break** in Gradle 9. This is **just a warning**, not the reason for your failure.

### To show detailed warnings:
You can run:

cordova build android -- --warning-mode all

Or:

cd platforms/android
./gradlew build --warning-mode all

This will list which plugins or scripts are using deprecated features, so you can plan for future upgrades.

—

## 🔚 Next Steps
1. **Fix the missing `ic_launcher` issue** first — it’s the real cause of build failure.
2. Then optionally check warnings using `–warning-mode all`.

Would you like me to send you default icon images (`ic_launcher.png` for all densities) to quickly fix the build?

—

### 🔍 Common Causes & Fixes

—

#### ✅ **1. Not Signed or Improperly Signed APK**
Android **does not allow installing unsigned release APKs**.

🔧 **Fix**: Sign your APK before installing:

cordova build android --release

Then **manually sign** it using your keystore:

jarsigner -verbose -sigalg SHA256withRSA -digestalg SHA-256 
-keystore my-release-key.keystore 
platforms/android/app/build/outputs/apk/release/app-release-unsigned.apk 
my-key-alias

Then **align** the APK:

zipalign -v 4 
platforms/android/app/build/outputs/apk/release/app-release-unsigned.apk 
app-release.apk

Then install the signed APK:

adb install app-release.apk

> You can also automate this with `build-extras.gradle`.

—

#### ✅ **2. APK Built for Incompatible Architecture or SDK**
If your device is old or has a lower Android version, and you built your app with a higher `minSdkVersion`, it will **fail to install**.

🔍 Check in `platforms/android/app/build.gradle`:

defaultConfig {
    minSdkVersion 22   // ✅ Lower this if needed
    targetSdkVersion 33
}

Check your device's Android version and match the minSdkVersion accordingly.

—

#### ✅ **3. Corrupted APK or Partial Download**
If the APK is corrupted or partially transferred (via email or browser), the Android OS can’t parse it.

🔧 Fix:
– Always transfer APK using `adb install` or proper file transfer (not WhatsApp, etc.).
– Try installing with:

adb install -r path/to/app-release.apk

—

#### ✅ **4. Invalid AndroidManifest.xml**
Misconfigured `AndroidManifest.xml` can break the APK build integrity.

You can inspect the manifest by:

unzip -p app-release.apk AndroidManifest.xml

Make sure:
– There are no missing icons
– There is a valid “ and “ tag

—

#### ✅ **5. APK File Extension Wrong**
Sometimes `.apk` gets saved as `.zip` or `.apk.apk`. Rename it properly.

—

### ✅ Recommended Debug Checklist

| Step | Action |
|——|——–|
| ✅ | Make sure APK is signed (`jarsigner`) |
| ✅ | Make sure APK is zipaligned |
| ✅ | Ensure `minSdkVersion` ≤ device Android version |
| ✅ | Use `adb install` to avoid file corruption |
| ✅ | Rename file properly to `.apk` |

—

Want me to walk you through signing your release APK step-by-step? Just share if you have a keystore already or need to generate one.

—

## ✅ FULL CHECKLIST TO FIX "There was a problem parsing the package" (Android Studio Signed APK)

—

### ✅ 1. **Check your `minSdkVersion`**
Make sure your APK can run on the Android version of your physical device.

#### 🔍 In `build.gradle` (Module: app)

defaultConfig {
    minSdkVersion 21  // Or lower if your device has an older Android version
    targetSdkVersion 33
}

💡 Example:
If your device runs **Android 6 (API 23)** and `minSdkVersion` is **24**, it will **not install**.

—

### ✅ 2. **Make Sure You're Installing the Right APK (Not App Bundle)**
If you're trying to install an `.aab` file (Android App Bundle), it **will not work** directly on a device.

#### 🔍 Solution:
Go to Android Studio:

**Build > Build Bundle(s) / APK(s) > Build APK(s)**
Then install the `.apk` from:

<your_project>/app/build/outputs/apk/release/app-release.apk

—

### ✅ 3. **Ensure You’re Not Using ABI splits (like arm64-v8a only)**
If you have split builds (e.g., only for `x86` or `arm64`), and your device doesn't support that architecture — you'll get this error.

#### 🔍 Check in `build.gradle`:

splits {
    abi {
        enable true
        reset()
        include 'armeabi-v7a', 'arm64-v8a'
        universalApk true
    }
}

If you're unsure, just build a **universal APK** (disable ABI splits).

—

### ✅ 4. **Reinstall or Use ADB to Install APK**
Sometimes file managers or downloads corrupt APKs.

#### Preferred method:

adb install -r app-release.apk

—

### ✅ 5. **Double-Check Your Signing Configuration**

In Android Studio:
– Go to **Build > Generate Signed Bundle/APK**
– Select **APK**
– Make sure:
– **Keystore path**, **alias**, and **passwords** are correct
– You selected **V1 (Jar Signature)** for compatibility with older devices

Older Android versions (API 23 and below) require **V1 signing**.

—

### ✅ 6. **Clean & Rebuild**

Sometimes leftover cache causes corrupt builds:

Build > Clean Project  
Build > Rebuild Project

Then rebuild the signed APK.

—

### ✅ Summary: Likely Fix
| Cause | Fix |
|——-|—–|
| `minSdkVersion` too high | Lower it to match your device |
| Using `.aab` | Use `.apk` |
| Only V2 signing used | Enable **V1** and **V2** in signing config |
| Device doesn't support build ABI | Enable **universal APK** or match architecture |
| APK corrupted on transfer | Use **ADB install** |

—

Would you like to send me your `build.gradle` or let me know the Android version of your device so I can confirm the correct `minSdkVersion`?

—

### ✅ Let's go step-by-step based on your case:

—

### ✅ 1. **Use `.apk` file, not `.aab`**

Make sure you're generating and installing a `.apk`, **not** a `.aab` (App Bundle).

#### In Android Studio:
Go to:
**`Build` > `Build Bundle(s) / APK(s)` > `Build APK(s)`**
👉 Then install the file located at:

<project-root>/app/build/outputs/apk/release/app-release.apk

—

### ✅ 2. **Enable V1 Signing (Jar Signature)**

Older devices need it, but even newer ones sometimes fail without it.

#### In Android Studio:
– Go to **`Build > Generate Signed Bundle / APK`**
– Choose **APK**, then click **Next**
– In **Signature Versions**, **check both**:
– ☑️ **V1 (Jar Signature)**
– ☑️ **V2 (Full APK Signature)**

> If only V2 is selected, the APK may fail to parse on some devices.

—

### ✅ 3. **Install APK Using ADB (Avoid Corruption)**

Sometimes transferring via WhatsApp, Gmail, etc., corrupts the APK.

Instead, connect your device via USB and run:

adb install -r path/to/app-release.apk

Or use Android Studio > **Device File Explorer > Upload APK & install**

—

### ✅ 4. **Check ABI Splits (Optional, if using splits)**

Make sure you’re not building the APK for an unsupported CPU architecture (like `x86`).

If in `build.gradle` you see:

splits {
    abi {
        enable true
        reset()
        include 'armeabi-v7a', 'arm64-v8a'
        universalApk true
    }
}

➡️ Make sure **`universalApk true`** is present, or just disable `splits` to generate one universal `.apk`.

—

### ✅ 5. **Clean & Rebuild the Project**

From Android Studio:
– `Build > Clean Project`
– `Build > Rebuild Project`
– Then `Build APK` again and reinstall.

—

### ✅ 6. **Don't Rename the APK Incorrectly**

Make sure the file is not saved as:

app-release.apk.apk

Or incorrectly renamed — it must be exactly `.apk`.

—

## 🔚 Summary — Your Best Fix Steps

# Recommended
1. Build > Generate Signed APK
2. Select .apk → Enable BOTH V1 and V2
3. Clean & Rebuild Project
4. Install via: adb install -r app-release.apk

Would you like me to double-check your `build.gradle` or show screenshots from Android Studio for this process?