瀏覽代碼

manually bump to 19.0.0 Alpha 02

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 <dev@mhibbe.de>
Marcel Hibbe 1 年之前
父節點
當前提交
fe82c3f061
共有 1 個文件被更改,包括 2 次插入2 次删除
  1. 2 2
      app/build.gradle

+ 2 - 2
app/build.gradle

@@ -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