Browser build – Step 4: Build the APK
Note
This is Step 4 of the Browser build. First complete Step 3 – Authorize Google Drive.
AAPS-CI GitHub Actions to Build the AAPS APK
Suitable for general users.
Run the Workflow to Build the Signed APK
In your GitHub copy of AndroidAPS, select Actions.
Expand All Workflows.
Select AAPS-CI
Scroll down and tap Run Workflow.
Select the branch you want to deploy (master), the variant (fullRelease) and tap Run Workflow.
You will see the message Workflow run was successfully requested. Refresh your browser page and you will be able to monitor the build progress. When the action completes, the AAPS CI action will show a green tick mark. You have successfully built the updated version of Android APS.
Install the AAPS APK
Open your Google Drive
Browse into AAPS, select the new version folder and you will find both the phone and Android Wear versions.
Build Version selection
Only AAPS versions from 3.3.2.1 and above will build with the Browser method.
Build Variants selection
Note: both Android and Android Wear apps will be built automatically.
Select the variant you need:
fullRelease: For regular pump usage with full functionality.
aapsclientRelease, aapsclient2Release: For caregivers (requires Nightscout)。
pumpcontrolRelease: To replace your pump app/controller
Variants ending with “Debug” indicates that the APK will be built in debug mode, which is useful for developers for troubleshooting.
Once the build succeeds, the apk is saved to your Google Drive. Continue with Transferring and Installing AAPS.
Note
From September 2026, Google’s Android developer verification may block installing the APK by tapping the file, depending on your country. Free workarounds are explained on that page.
If anything goes wrong, see Browser build troubleshooting. To include a specific commit in your build, see cherry-pick a commit.