Skip to content

Changed app version to 2.60 in manifest #3306

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OrangeAndGreen merged 1 commit into from
Aug 25, 2025
Merged

Changed app version to 2.60 in manifest #3306

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion app/AndroidManifest.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:versionCode="106"
android:versionName="2.59.0">
android:versionName="2.60">
Comment on lines 4 to +5
Copy link

@coderabbitai coderabbitai bot Aug 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Release-blocker: Bump android:versionCode for Play upload

Updating only versionName will not be accepted by Play if versionCode remains 106; every release must increment versionCode. Recommend setting it to 107 (or next unused integer per your release train).

Apply this diff:

-          android:versionCode="106"
-          android:versionName="2.60">
+          android:versionCode="107"
+          android:versionName="2.60">
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
android:versionCode="106"
android:versionName="2.59.0">
android:versionName="2.60">
android:versionCode="107"
android:versionName="2.60">
🤖 Prompt for AI Agents 
In app/AndroidManifest.xml around lines 4 to 5, the android:versionCode is still
106 which blocks Play upload because versionCode must be incremented for each
release; update android:versionCode to the next integer (e.g., 107) while
keeping android:versionName as desired, save the manifest, and verify the build
uses the updated manifest before submitting to the Play Console.

💡 Verification agent

🧩 Analysis chain

Verify the manifest is the source of truth (Gradle can override these)

Many Android builds set versionCode/versionName in build.gradle(defaultConfig). If that’s the case here, this manifest change will be ignored. Please confirm there are no overrides in Gradle or flavors.

Run from repo root:

🏁 Script executed:

#!/bin/bash
# Find any Gradle overrides of versionCode/versionName
rg -nP -C2 '^\s*version(Code|Name)\s' --glob '!**/build/**' --type-add 'gradle:*.gradle' --type-add 'kts:*.kts' --type gradle --type kts
echo "Manifest occurrences:"
rg -nP -C1 'android:(versionCode|versionName)=' app/src/main/AndroidManifest.xml app/AndroidManifest.xml 2>/dev/null || true

Length of output: 750

Manifest version values are being overridden by Gradle defaultConfig – please fix

We discovered that your AndroidManifest.xml entries…

  • android:versionCode="106"
  • android:versionName="2.60"

…are effectively ignored at build time because in app/build.gradle (around line 290) you have:

defaultConfig {
    // …
    versionCode 1
    // (no versionName set here)
    // …
}

This means:

  • Gradle uses versionCode 1 instead of 106, so your manifest bump to 106 has no effect.
  • Since versionName isn’t set in Gradle, only the manifest’s 2.60 will be used—but best practice is to manage both in Gradle for consistency.

To resolve:

• Option A – Define both values in Gradle and remove them from the manifest

--- a/app/build.gradle
+++ b/app/build.gradle
 defaultConfig {
-    versionCode 1
+    versionCode 106
+    versionName "2.60"
     // …
 }
--- a/app/AndroidManifest.xml
+++ b/app/AndroidManifest.xml
-    android:versionCode="106"
-    android:versionName="2.60"

• Option B – Keep definitions in the manifest and remove overrides from Gradle

--- a/app/build.gradle
+++ b/app/build.gradle
 defaultConfig {
-    versionCode 1
+    // versionCode/versionName managed in AndroidManifest.xml
     // …
 }

Also double-check any productFlavor or buildType blocks for further versionCode/versionName overrides.

🤖 Prompt for AI Agents 
In app/AndroidManifest.xml around lines 4-5 the manifest sets
android:versionCode="106" and android:versionName="2.60" but these are being
overridden by app/build.gradle defaultConfig (versionCode 1) so the manifest
changes have no effect; fix by moving versionCode and versionName management to
Gradle (preferred): set both versionCode and versionName in app/build.gradle
defaultConfig (and remove them from AndroidManifest.xml), or alternatively
remove the overrides from Gradle so the manifest values are used; also scan
productFlavors and buildType blocks for any additional versionCode/versionName
overrides and reconcile them.


<uses-permission android:name="android.permission.NFC"/>
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/>
Expand Down
Loading