diff --git a/vector/build.gradle b/vector/build.gradle
index b9e01ed0..4cec152f 100644
--- a/vector/build.gradle
+++ b/vector/build.gradle
@@ -71,10 +71,21 @@ android {
         testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
     }
 
+    signingConfigs {
+        debug {
+            keyAlias 'androiddebugkey'
+            keyPassword 'android'
+            storeFile file('./signature/debug.keystore')
+            storePassword 'android'
+        }
+    }
+
     buildTypes {
         debug {
             resValue "bool", "debug_mode", "true"
             buildConfigField "boolean", "LOW_PRIVACY_LOG_ENABLE", "false"
+
+            signingConfig signingConfigs.debug
         }
 
         release {
diff --git a/vector/signature/README.md b/vector/signature/README.md
new file mode 100644
index 00000000..7d9005f1
--- /dev/null
+++ b/vector/signature/README.md
@@ -0,0 +1,12 @@
+
+## Debug signature
+
+Buildkite CI tool uses docker images to build the Android application, and it looks like the debug signature is changed at each build.
+
+So it's not possible for user to upgrade the application with the last build from buildkite without uninstalling the application.
+
+This folder contains a debug signature, and the debug build will uses this signature to build the APK.
+
+The validity of the signature is 30 years. So it has to be replaced before June 2049 :).
+
+More info about the debug signature: https://developer.android.com/studio/publish/app-signing#debug-mode
diff --git a/vector/signature/debug.keystore b/vector/signature/debug.keystore
new file mode 100644
index 00000000..4a15fc9e
Binary files /dev/null and b/vector/signature/debug.keystore differ