Option 2 – Upload your existing keystore
Note
This is part of Step 2 – Create your signing keystore of the Browser build. Make sure you have read the Option 1 vs Option 2 decision and downloaded the preparation file.
Option 2 reuses the JKS you already created on a previous build of AAPS from a computer in Android Studio. It is suitable for users who already have a JKS and know the JKS password and alias.
For KEYSTORE_PASSWORD, KEY_ALIAS, and KEY_PASSWORD, enter your actual password and alias in GitHub – those from Android Studio, see below where you used them.
Warning
Passwords with special characters. If your keystore or key password contains $, a backtick, " or \, the build fails at the signing step even though the password is correct. When you enter the secret in GitHub, put a backslash \ in front of each of these four characters only.
Example: if your password is abc$def"ghi, enter abc\$def\"ghi.
Every other character, including %, *, # and !, must be entered exactly as it is. Adding a backslash in front of them would become part of the password. See Browser build troubleshooting.
KEY + PASSWORDS
Choose your device
Follow the page that matches the device you are building from:
Tip
You can switch device at any time – just open the matching page.