Set the ant keystore properties earlier

build/android/ant/apk-build.xml

 <?xml version="1.0" encoding="UTF-8"?>
 <!--
     Copyright (C) 2005-2008 The Android Open Source Project
 
     Licensed under the Apache License, Version 2.0 (the "License");
     you may not use this file except in compliance with the License.
     You may obtain a copy of the License at
 
          http://www.apache.org/licenses/LICENSE-2.0
 
@@ skipping 244 matching lines @@
     <property name="out.build.prop.file" location="${out.absolute.dir}/build.prop" />
 
 
     <!-- This is needed by emma as it uses multilevel verbosity instead of simple 'true' or 'false'
          The property 'verbosity' is not user configurable and depends exclusively on 'verbose'
          value.-->
     <condition property="verbosity" value="verbose" else="quiet">
         <istrue value="${verbose}" />
     </condition>
 
+    <!--
+      For debug builds, the Android SDK tools create a key in ~/.android and sign the build with it.
+      This has caused all kinds of issues. Instead, the debug build should be signed with a key in
+      build/android/ant. The SDK tools do not provide any support for overriding that behavior and so
+      instead one must use the hack below.
+    -->
+    <property name="key.store" value="${CHROMIUM_SRC}/build/android/ant/chromium-debug.keystore"/>
+    <property name="key.store.password" value="chromium"/>
+    <property name="key.alias" value="chromiumdebugkey"/>
+    <property name="key.alias.password" value="chromium"/>
+
+
     <!-- properties for signing in release mode -->
     <condition property="has.keystore">
         <and>
             <isset property="key.store" />
             <length string="${key.store}" when="greater" length="0" />
             <isset property="key.alias" />
         </and>
     </condition>
     <condition property="has.password">
         <and>
@@ skipping 870 matching lines @@
         <!-- Renderscript optimization level: none -->
         <property name="renderscript.opt.level" value="${renderscript.debug.opt.level}" />
 
     </target>
 
     <target name="-debug-obfuscation-check">
         <!-- proguard is never enabled in debug mode -->
         <property name="proguard.enabled" value="false"/>
     </target>
 
-    <!--
-      For debug builds, the Android SDK tools create a key in ~/.android and sign the build with it.
-      This has caused all kinds of issues. Instead, the debug build should be signed with a key in
-      build/android/ant. The SDK tools do not provide any support for overriding that behavior and so
-      instead one must use the hack below.
-    -->
-    <property name="key.store" value="${CHROMIUM_SRC}/build/android/ant/chromium-debug.keystore"/>
-    <property name="key.store.password" value="chromium"/>
-    <property name="key.alias" value="chromiumdebugkey"/>
-    <property name="key.alias.password" value="chromium"/>
-
     <!-- SDK tools assume that out.packaged.file is signed and name it "...-unaligned" -->
     <property name="out.packaged.file"
       value="${apks.dir}/${ant.project.name}-unsigned.apk" />
     <property name="out.unaligned.file"
       value="${apks.dir}/${ant.project.name}-unaligned.apk" />
 
     <!-- By default, the SDK tools build only aligns the APK in the -do-debug target. -->
     <!-- Builds debug output package -->
     <target name="-do-debug"
         depends="-set-debug-mode, -debug-obfuscation-check, -package, -post-package">
@@ skipping 507 matching lines @@
         <echo>   installd:  Installs (only) the debug package.</echo>
         <echo>   installr:  Installs (only) the release package.</echo>
         <echo>   installi:  Installs (only) the instrumented package.</echo>
         <echo>   installt:  Installs (only) the test and tested packages (unless</echo>
         <echo>              nodeps is used as well.</echo>
         <echo>   uninstall: Uninstalls the application from a running emulator or</echo>
         <echo>              device. Also uninstall tested package if applicable</echo>
         <echo>              unless 'nodeps' is used as well.</echo>
     </target>
 </project>