Skip to content

Commit

Permalink
manually bump to 19.0.0 Alpha 02
Browse files Browse the repository at this point in the history
there seems to be something wrong that alpha workflow did not update the apps version.
Thats why gplay complains with
"Google Api Error: forbidden: Cannot update a published APK. - Cannot update a published APK."
because it always tries to upload 19.0.0 Alpha 02.

On nextcloud ftp server, it was most probably always overwritten as there is an up to date alpha2 version.

Seeting the version number to 19.0.0 Alpha 02 should make sure that an alpha 3 is built on next automation run.

The root cause that the version was/is not changed by the automation is still unclear.

Signed-off-by: Marcel Hibbe <[email protected]>
  • Loading branch information
mahibi committed Mar 19, 2024
1 parent 325da27 commit fe82c3f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions app/build.gradle
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,8 @@ android {

// mayor.minor.hotfix.increment (for increment: 01-50=Alpha / 51-89=RC / 90-99=stable)
// xx .xxx .xx .xx
versionCode 190000001
versionName "19.0.0 Alpha 01"
versionCode 190000002
versionName "19.0.0 Alpha 02"

flavorDimensions "default"
renderscriptTargetApi 19
Expand Down

0 comments on commit fe82c3f

Please sign in to comment.