# Bitrise Workflow Quirks We currently have four workflows which generate builds: * `build-demo-sand-prod-apks`: This workflow **builds** the APKs for all environments (`SANDBOX`, `DEMO`, `PRODUCTION`) and makes them available for download. * `deploy-sandbox-to-play-store`: This workflow **builds** the `SANDBOX` APK **and** deploys it to the Play Store. * `deploy-demo-to-play-store`: This workflow **builds** the `DEMO` APK **and** deploys it to the Play Store. * `deploy-prod-to-play-store`: This workflow **builds** the `PRODUCTION` APK **and** deploys it to the Play Store. The quirk here to note is that the gradle build command is duplicated across all of these builds. The gradle config for `build-demo-sand-prod-apks` is hardcoded as part of the workflow, whereas for the others, there are sub-workflows named `_gradle-sandbox-build`, `_gradle-sandbox-build`, and `_gradle-prod-build` respectively. Currently, if you need to make a change to the gradle build command, you need to make the change in **ALL** of these workflows. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.simple.org/engineering/android/bitrise-workflow-quirks.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.