Mr Bauri
Відкрити в Telegram
🙏Thanks for Visiting My Telegram Channel🙏 🔰Video Creater 🎬 (CHHOTON BAURI)
Показати більше2 556
Підписники
Немає даних24 години
Немає даних7 днів
Немає даних30 днів
Триває завантаження даних...
Схожі канали
Хмара тегів
Немає даних
Виникли проблеми? Будь ласка, оновіть сторінку або зверніться до нашого support-менеджера.
Вхідні та вихідні згадування
---
---
---
---
---
---
Залучення підписників
жовтень '26жовт '26
жовтень '260
в 0 каналах
вересень '260
в 0 каналах
Get PRO
серпень '260
в 0 каналах
Get PRO
липень '260
в 0 каналах
Get PRO
червень '260
в 0 каналах
Get PRO
травень '260
в 0 каналах
Get PRO
квітень '260
в 0 каналах
Get PRO
березень '260
в 0 каналах
Get PRO
лютий '260
в 0 каналах
Get PRO
січень '260
в 0 каналах
Get PRO
грудень '250
в 0 каналах
Get PRO
листопад '250
в 0 каналах
Get PRO
жовтень '250
в 0 каналах
Get PRO
вересень '250
в 0 каналах
Get PRO
серпень '250
в 0 каналах
Get PRO
липень '250
в 0 каналах
Get PRO
червень '250
в 0 каналах
Get PRO
травень '250
в 0 каналах
Get PRO
квітень '250
в 0 каналах
Get PRO
березень '250
в 0 каналах
Get PRO
лютий '250
в 0 каналах
Get PRO
січень '250
в 0 каналах
Get PRO
грудень '24
+1
в 0 каналах
Get PRO
листопад '24
+1
в 0 каналах
Get PRO
жовтень '24
+4
в 0 каналах
Get PRO
вересень '24
+22
в 0 каналах
Get PRO
серпень '24
+29
в 0 каналах
Get PRO
липень '24
+42
в 0 каналах
Get PRO
червень '24
+46
в 0 каналах
Get PRO
травень '24
+38
в 0 каналах
Get PRO
квітень '24
+70
в 0 каналах
Get PRO
березень '24
+149
в 0 каналах
Get PRO
лютий '24
+77
в 0 каналах
Get PRO
січень '24
+4 463
в 0 каналах
| Дата | Залучення підписників | Згадування | Канали | |
| 13 жовтня | 0 | |||
| 12 жовтня | 0 | |||
| 11 жовтня | 0 |
Дописи каналу
| 2 | If I provide an existing application/project:
DO NOT redesign it.
DO NOT remove existing features.
DO NOT change working functionality unnecessarily.
DO NOT replace working API integration unnecessarily.
DO NOT change the UI unless I specifically request it.
Only modify what is required to make the application production-ready and GitHub Release APK compatible.
---
16. FINAL RESPONSE
After completing the project, provide a clear summary containing:
A. Application
- App name
- Package name
- Version
B. Files Created/Modified
List the important files.
C. GitHub Actions
Tell me the exact workflow file location.
D. Required GitHub Secrets
List the exact secret names.
E. Signing
Explain how I create and configure the signing keystore.
F. Build
Give the exact steps to manually generate the Release APK.
G. Automatic Release
Explain how to create:
v1.0.0
and trigger the automatic GitHub Release.
H. APK Location
Explain exactly where I can download the generated APK.
I. Phone Installation
Explain how I can install the APK on my Android phone.
---
MOST IMPORTANT REQUIREMENT
The final project must be:
Android Project → GitHub → GitHub Actions → Signed Release APK → GitHub Release → Download → Android Installation
Make this workflow as automated and beginner-friendly as possible.
Do not simply give me instructions.
Actually create/configure the required files in the project so that after I push the project to GitHub and configure the required secrets, I can generate the signed Release APK through GitHub Actions.
If something cannot be automated because it requires a secret, certificate, account authorization, or manual GitHub setting, clearly identify that specific step and explain exactly what I need to do manually. | 140 |
| 3 | 1. Checkout the repository.
2. Set up the required Java version.
3. Set up Android SDK if necessary.
4. Configure Gradle.
5. Restore Gradle cache where appropriate.
6. Configure required environment variables.
7. Configure Android signing.
8. Build the Release APK.
9. Verify the APK exists.
10. Rename the APK using the app name and version.
11. Upload the APK as a GitHub Actions artifact.
12. When triggered by a version tag, attach the APK to a GitHub Release.
Example filename:
APP-NAME-v1.0.0-release.apk
Replace APP-NAME with the actual application name.
---
8. PRODUCTION ANDROID SIGNING
Set up secure production signing.
DO NOT commit the signing keystore into GitHub.
The GitHub Actions workflow must support these GitHub Secrets:
ANDROID_KEYSTORE_BASE64
ANDROID_KEYSTORE_PASSWORD
ANDROID_KEY_ALIAS
ANDROID_KEY_PASSWORD
The workflow should:
- Decode the Base64 keystore temporarily.
- Use it for Release signing.
- Never print secrets in logs.
- Delete the temporary keystore after the build.
The final APK must be a properly signed Release APK.
Do NOT use a debug APK as the production artifact.
---
9. KEYSTORE SETUP DOCUMENTATION
In README.md explain clearly:
1. How to generate a production Android keystore.
2. How to keep the keystore safe.
3. How to convert the keystore to Base64.
4. How to add the required secrets to:
GitHub → Repository → Settings → Secrets and variables → Actions
5. How to run the Release workflow.
Never put an actual password or secret into README.md.
---
10. VERSION MANAGEMENT
Make version management easy.
Default:
versionName = "1.0.0"
versionCode = 1
Explain how I can update the version for future releases.
For example:
1.0.1
1.1.0
2.0.0
Make sure Android versionCode increases for every production update.
---
11. GITHUB RELEASE
When I create:
v1.0.0
the GitHub Action should:
- Build the Release APK.
- Verify the APK.
- Create a GitHub Release.
- Name it:
[APP NAME] v1.0.0
- Attach the APK.
- Add a short release description.
Example:
[APP NAME] v1.0.0
Initial production release.
---
12. APK DISTRIBUTION
The generated APK must be a normal signed Android APK suitable for legitimate manual distribution.
I may distribute the APK through:
- My own website
- GitHub Releases
- Social media
- Legitimate Android software distribution platforms
Examples may include:
Uptodown
APKPure
Softonic
and similar legitimate platforms.
Do not add anything designed to bypass security or platform rules.
The application must comply with applicable platform policies.
---
13. README.md
Create a professional README.md containing:
App Overview
What the application does.
Features
List the major features.
Requirements
Required tools and SDK versions.
Local Development
Explain how to run the project locally.
Environment Variables
Explain every required variable.
GitHub Setup
Explain how to push the project to GitHub.
Android Signing
Explain how to create and configure the production keystore.
GitHub Secrets
Explain every required secret.
Release APK
Explain:
- How to manually run the workflow.
- How to create a version tag.
- How to download the APK.
- Where the APK will appear.
Android Installation
Explain how to install the APK on an Android phone.
---
14. QUALITY CHECK
Before finishing the project, inspect the entire project.
Check:
- Build configuration
- Gradle files
- AndroidManifest
- Package/Application ID
- Dependencies
- Resource files
- Environment variables
- API configuration
- Release signing configuration
- GitHub Actions YAML
- README
- .gitignore
Fix any obvious build errors.
Do not leave broken references.
Do not reference files that do not exist.
Do not use incorrect Gradle module names.
Make sure the GitHub workflow uses the actual module and actual Gradle task of this project.
For example, if the Android module is "app", use the correct task such as:
./gradlew :app:assembleRelease
Do not blindly assume the module name if the project structure is different.
---
15. IMPORTANT — DO NOT BREAK MY APPLICATION | 95 |
| 4 | UNIVERSAL ANDROID APP DEVELOPMENT + GITHUB + RELEASE APK MASTER PROMPT
I want you to build and configure my Android application as a complete, production-ready Android project.
APP INFORMATION
App Name:
[APP NAME]
Package/Application ID:
[COM.APP.PACKAGE.NAME]
App Description:
[DESCRIBE WHAT THE APP DOES]
Version:
1.0.0
Version Code:
1
The application must be designed for real Android devices and must be suitable for production distribution.
---
1. BUILD THE COMPLETE APPLICATION
Build the complete Android application based on my requirements.
The application must have:
- Modern professional UI
- Mobile-first responsive design
- Smooth navigation
- Proper loading states
- Proper empty states
- Proper error handling
- Offline/error-state handling where appropriate
- Android back-button handling
- Proper keyboard handling
- Proper screen scrolling
- Accessible buttons and touch targets
- Good performance
- Production-quality code
- Clean project structure
Do not create a demo-only application.
Do not leave important features as fake placeholders unless I explicitly request them.
If an API/backend is required, structure the application properly so it can connect to the real API/backend.
---
2. ANDROID PROJECT REQUIREMENTS
The final project must be a genuine Android project that can be built with Gradle.
Make sure:
- Android application module exists.
- Gradle configuration is valid.
- Android Gradle Plugin and Gradle versions are compatible.
- Java/Kotlin configuration is compatible.
- Min SDK is appropriate for modern Android devices.
- Target SDK is a currently supported Android API level.
- Application ID is valid.
- Version name and version code are configurable.
- AndroidManifest.xml is valid.
- Required permissions are correctly configured.
- Internet permission is included when the application requires internet/API access.
- Release build configuration is valid.
- Debug and Release configurations are separated correctly.
Do not use experimental or unnecessary dependencies.
Use stable versions whenever possible.
---
3. SECURITY
Never hard-code sensitive information inside the source code.
Do not expose:
- API keys
- Secret keys
- Passwords
- Access tokens
- Private keys
- Signing keystores
- Database credentials
Use environment variables or secure configuration.
For example:
APP_API_KEY
YOUTUBE_API_KEY
BACKEND_BASE_URL
If the application needs a backend, structure the app so sensitive API credentials can remain server-side whenever possible.
Do not create any security bypass.
Do not bypass Android security, Play Protect, authentication systems, payment systems, or platform restrictions.
---
4. ENVIRONMENT VARIABLES
Make the project compatible with environment variables.
If my application requires variables, document them clearly.
Example:
YOUTUBE_API_KEY
BACKEND_BASE_URL
APP_API_KEY
Do not commit real secret values to GitHub.
Create an example configuration file if appropriate, such as:
.env.example
The example file must contain placeholders only.
---
5. GITHUB-READY PROJECT
Prepare the project so I can push it directly to GitHub.
Create/update:
README.md
.gitignore
Make sure the following are excluded from Git:
- build/
- .gradle/
- local.properties
- generated files
- keystores
- secret files
- API credentials
- temporary files
The repository must be clean and safe to publish publicly.
---
6. AUTOMATIC GITHUB RELEASE APK BUILD
Create this GitHub Actions workflow:
.github/workflows/release-apk.yml
The workflow must support:
workflow_dispatch
and version tags such as:
v1.0.0
v1.0.1
v2.0.0
When I manually run the workflow, it must build a Release APK.
When I push a version tag, it should automatically build the Release APK and create a GitHub Release.
---
7. RELEASE BUILD
The workflow must: | 95 |
| 5 | https://veoaifree.com/ | 135 |
| 6 | Calculator-Apk-debug-build-2.apk | 212 |
| 7 | Google ai.txt | 236 |
| 8 | If my next message contains only a repository identity in this format:
username/repository-name
example:
appsteck/daily-quote-apk
do the following:
1. Treat the first part as the GitHub owner/username.
2. Treat the second part as the GitHub repository name.
3. Do not modify any project file.
4. Do not create another workflow.
5. Do not rebuild the Android app.
6. Do not ask additional questions.
7. Do not attempt to publish anything.
8. Construct this URL using the exact repository name I provided:
https://github.com/USERNAME/REPOSITORY/releases/latest/download/app-debug.apk
Then respond very briefly using this format:
================================
📱 DIRECT APK DOWNLOAD
https://github.com/USERNAME/REPOSITORY/releases/latest/download/app-debug.apk
Your GitHub Actions APK build started when you published/pushed the project.
Allow approximately 7–9 minutes for the build and GitHub Release process to finish.
If the link is not ready yet, wait a little longer and try again.
Once the release finishes, paste this link into Chrome to download app-debug.apk directly.
================================
Do not add unnecessary instructions.
Do not send me to the GitHub Actions page unless the direct APK link still does not work after the build has had enough time to complete.
Do not change the URL format.
Do not use a release tag in the URL.
Do not replace app-debug.apk with another filename.
---
Do not publish, commit, sync, push, tag, or manually create a GitHub Release now.
Create only the workflow file and wait for me to manually publish/push the project to GitHub.
________________
Prompt End
—------------- | 240 |
| 9 | If release publishing succeeded:
- Confirm the release using gh release view.
- Print the release tag.
- Print the release title.
- Print the release page URL.
- Print the APK filename:
app-debug.apk
- Construct the latest direct APK URL internally using:
https://github.com/${GITHUB_REPOSITORY}/releases/latest/download/app-debug.apk
- Add the direct APK URL to GITHUB_STEP_SUMMARY.
- Label it:
DIRECT APK DOWNLOAD
- State that the normal Actions artifact app-debug-apk remains available as a backup.
If release publishing failed:
- Print a clear warning.
- State that the APK build succeeded if it did.
- State that app-debug-apk remains available.
- Do not falsely claim the new APK is available through the direct latest-release link.
Authenticate gh commands using:
GH_TOKEN: ${{ github.token }}
---
# 18. Security restrictions
Do not create fake:
- google-services.json
- Firebase files
- API keys
- Credentials
- Personal access tokens
- Release signing files
- Production keystores
- Missing secrets
- Placeholder secrets
Do not expose:
- GITHUB_TOKEN
- GH_TOKEN
- Environment credentials
- Repository secrets
- Keystore contents
Do not echo authentication tokens into workflow logs.
Do not persist credentials beyond the temporary GitHub Actions runner.
Do not modify repository settings.
Do not enable GitHub Pages.
Do not create a website.
Do not create a download website.
Do not create a second workflow.
Do not commit an APK to the source repository.
Do not create a GitHub Release manually while preparing the project.
The release must be created only when the generated workflow runs after I publish/push the project to GitHub.
---
# 19. Final workflow validation
Before finishing, confirm:
- Only .github/workflows/build-apk.yml was created.
- No existing file was modified.
- AGP 9.1.1 was confirmed.
- Java 17 is configured before Gradle.
- Active Java version is verified.
- Exactly Gradle 9.3.1 is used.
- Repository Gradle wrapper is not used.
- Temporary debug keystore is created before building.
- Temporary keystore is never uploaded.
- Build command is exactly:
gradle :app:assembleDebug --stacktrace --no-daemon
- APK path is exactly:
app/build/outputs/apk/debug/app-debug.apk
- Actions artifact name is exactly:
app-debug-apk
- Actions artifact is uploaded before release publishing.
- Release asset is a real APK and not a ZIP.
- Release asset filename is exactly:
app-debug.apk
- Every workflow execution receives a unique release tag.
- GITHUB_RUN_NUMBER and GITHUB_RUN_ATTEMPT are used in the tag.
- Release targets GITHUB_SHA.
- New successful release is marked latest.
- Built-in GitHub token is used.
- contents: write permission is configured.
- No personal access token is needed.
- No repository secret is needed.
- Release failure leaves the Actions artifact available.
- No Android application/project file was changed.
- No APK was committed to the source repository.
- Permanent APK URL uses:
/releases/latest/download/app-debug.apk
---
# 20. FIRST RESPONSE — KEEP THIS VERY SHORT
After creating the workflow, do NOT give me a long explanation.
Give me only a short summary similar to:
APK BUILD WORKFLOW READY
AGP:
9.1.1
Java:
17+
Gradle:
9.3.1
APK:
app/build/outputs/apk/debug/app-debug.apk
Release APK:
app-debug.apk
Then display:
NEXT STEP
Publish/push this app to GitHub now.
This first GitHub push will also trigger the automatic APK build because the workflow is already included in the project.
After GitHub creates the repository, return to this Gemini chat and paste ONLY the full repository name.
Use this format:
username/repository-name
Example:
myusername/my-android-app
Do not paste anything else.
I will generate your permanent direct APK download link.
Do NOT try to detect the repository automatically.
Do NOT invent a repository name.
Wait for me to provide it.
---
# 21. FOLLOW-UP BEHAVIOR AFTER I PROVIDE THE REPOSITORY NAME | 168 |
| 10 | Do not use an unverified third-party GitHub Release action.
Authenticate using:
GH_TOKEN: ${{ github.token }}
Before release creation:
- Run gh --version.
- Confirm GitHub CLI is available.
- Confirm the prepared APK exists.
- Confirm it is non-empty.
- Confirm it ends in .apk.
- Confirm the release asset filename is exactly app-debug.apk.
- Do not attempt release creation if APK validation fails.
---
# 13. Unique GitHub Release tag
Every workflow execution must receive a unique release tag using both:
GITHUB_RUN_NUMBER
and:
GITHUB_RUN_ATTEMPT
Use this tag format:
debug-apk-build-GITHUB_RUN_NUMBER-GITHUB_RUN_ATTEMPT
Example:
debug-apk-build-12-1
Construct the tag dynamically at workflow runtime.
Do not use a fixed tag such as:
- latest
- debug
- build
- v1
- apk
Do not overwrite, move, delete, or reuse an existing release tag.
The unique tag must prevent conflicts when:
- A new commit is pushed.
- The workflow is run manually.
- A failed workflow is rerun.
- Another run attempt occurs.
---
# 14. GitHub Release contents
Create a published GitHub Release.
Release title:
Debug APK Build #GITHUB_RUN_NUMBER
Release tag:
debug-apk-build-GITHUB_RUN_NUMBER-GITHUB_RUN_ATTEMPT
Target commit:
GITHUB_SHA
Release notes must clearly state:
- This is an automatically generated debug APK.
- The APK was built by GitHub Actions.
- GitHub Actions run number.
- GitHub Actions run attempt.
- Source commit SHA.
- APK is intended for testing.
- APK is not a Play Store production release.
- APK is signed only with a temporary debug keystore.
Attach only:
app-debug.apk
as the manually uploaded release asset.
Do not manually attach:
- ZIP files
- Source-code archives
- tar.gz files
- debug.keystore
- Credentials
- Configuration files
- Gradle files
- Build caches
- Logs
- Secrets
- Any unrelated APK
GitHub may automatically display its standard:
Source code (zip)
and:
Source code (tar.gz)
links.
Do not attempt to create, upload, replace, remove, or modify those platform-generated links.
Mark the newly created successful release explicitly as the latest release using:
--latest
Do not create the release as:
- Draft
- Prerelease
- Immutable release requiring later manual publication
The release Assets section must contain:
app-debug.apk
---
# 15. Permanent APK direct-download system
The GitHub Release asset filename must always remain:
app-debug.apk
Because the newest successful release is marked as latest, the permanent APK download URL format is:
https://github.com/USERNAME/REPOSITORY/releases/latest/download/app-debug.apk
Do NOT use:
- GitHub Actions artifact URLs
- Temporary URLs
- A specific release tag URL
- A run-number URL
- A release page as the primary download link
The permanent URL must always use:
/releases/latest/download/app-debug.apk
Do not attempt to determine USERNAME or REPOSITORY before the GitHub repository exists.
Do not invent the repository identity.
I will provide the full GitHub repository name after publishing the project.
---
# 16. Release failure protection
The GitHub Actions artifact must upload BEFORE release publishing begins.
Configure the release publishing step with:
continue-on-error: true
Assign an id to the release step so its outcome can be checked afterward.
If release publishing fails:
- Do not remove the successfully built APK.
- Do not remove the Actions artifact.
- Do not falsely report release success.
- Do not create a duplicate fallback release.
- Do not use another release action.
- Clearly report that the release failed.
- Clearly state that the Actions artifact named app-debug-apk remains available.
Release failure must not make a successful APK build appear to have failed if the APK and Actions artifact were successfully generated.
---
# 17. Report APK result
After the release attempt, add a step named:
Report APK download result
This step must always run after the release attempt. | 85 |
| 11 | That step must:
- Run java -version.
- Print JAVA_HOME.
- Detect the active Java major version.
- Confirm the active Java version is 17 or newer.
- Fail clearly if Java is lower than 17.
- Fail clearly if Java cannot be detected.
---
# 6. Gradle setup
Set up exactly:
Gradle 9.3.1
using:
gradle/actions/setup-gradle
Do not use:
- Gradle 8.13
- Repository Gradle wrapper
- ./gradlew
- gradlew
- latest
- current
- release-candidate
- nightly
- Any Gradle version other than exactly 9.3.1
Run all Gradle commands from the repository root.
---
# 7. Temporary debug keystore
Before building, add a step named:
Create temporary debug keystore
That step must:
- Check whether ./debug.keystore already exists.
- Generate it only when it is missing.
- Use keytool from the configured Java installation.
Use exactly:
Keystore password:
android
Key alias:
androiddebugkey
Key password:
android
Distinguished name:
CN=Android Debug,O=Android,C=US
Algorithm:
RSA
Key size:
2048
Validity:
10000 days
After generation:
- Confirm ./debug.keystore exists.
- Fail clearly if it cannot be created.
Never:
- Commit the keystore.
- Cache the keystore.
- Print the keystore.
- Expose its contents.
- Upload the keystore as an artifact.
- Upload the keystore to GitHub Releases.
- Preserve the keystore outside the temporary GitHub Actions runner.
---
# 8. Build the debug APK
Build the debug APK using exactly:
gradle :app:assembleDebug --stacktrace --no-daemon
Do not replace this command with:
- ./gradlew
- gradlew
- assembleRelease
- bundleRelease
- assemble
- build
- Any other Gradle build command
---
# 9. Verify the APK
After the build, verify that this exact file exists:
app/build/outputs/apk/debug/app-debug.apk
If the exact file is missing:
- Search only inside app/build/outputs/apk.
- Print APK paths discovered there.
- Do not search the entire repository.
- Do not select a release APK.
- Do not select an Android test APK.
- Do not select an APK from another module.
- Do not upload or release an unrelated APK.
- Fail clearly.
Confirm that the APK:
- Exists.
- Is a regular file.
- Is not empty.
- Has the .apk extension.
- Is exactly:
app/build/outputs/apk/debug/app-debug.apk
---
# 10. Upload GitHub Actions backup artifact
After APK verification, add a step named:
Upload debug APK artifact
Use:
actions/upload-artifact
Upload only:
app/build/outputs/apk/debug/app-debug.apk
Name the Actions artifact exactly:
app-debug-apk
Configure artifact upload to fail if the APK is missing.
Do not upload:
- debug.keystore
- Credentials
- Source code
- Gradle caches
- Build caches
- Configuration files
- Secrets
- Logs containing sensitive information
- google-services.json
- Firebase configuration
- Signing files
The normal Actions artifact must remain available as a backup even after GitHub Release publishing is added.
---
# 11. Prepare APK release asset
After the Actions artifact is uploaded successfully, add a step named:
Prepare APK release asset
Create a temporary directory inside the GitHub Actions runner.
Do not create or commit this directory in the repository.
Copy only:
app/build/outputs/apk/debug/app-debug.apk
into the temporary directory.
The GitHub Release asset filename MUST ALWAYS be exactly:
app-debug.apk
Do not add:
- Repository name
- Workflow run number
- Workflow attempt
- Commit SHA
- Date
- Timestamp
- Version number
- Random characters
Every GitHub Release must contain its APK using the same asset filename:
app-debug.apk
Do not compress the APK.
Do not place the APK inside a ZIP.
Do not rename the original APK inside the repository.
Do not modify the original APK.
Export the prepared release asset path through GITHUB_OUTPUT.
---
# 12. Publish APK to GitHub Releases
After the normal Actions artifact is uploaded and the release asset is prepared, add a step named:
Publish APK to GitHub Releases
Use:
gh release create | 88 |
| 12 | How to Download APK from Google AI Studio Android App
Thank you for watching this N-Educate tutorial.
In this video, you will learn how to prepare your completed Google AI Studio Android app so GitHub Actions can automatically build the debug APK, publish it to GitHub Releases, and give you a direct APK download link you can open in your browser.
For further assistance, support, and access to more prompts, codes, and step-by-step resources, join our Skool community using the link in the video description.
________________
Google AI Studio Prompt to Automatically Build and Download Android APK with GitHub Actions
________________
Prompt Start Here
—---------------------
Prepare this completed Google AI Studio Android app for automatic debug APK building and direct APK downloading through GitHub Actions and GitHub Releases.
IMPORTANT WORKFLOW:
You must first create the GitHub Actions APK build workflow inside this project.
Do NOT require the GitHub repository to already exist.
After creating the workflow, give me a very short NEXT STEP instruction telling me to:
1. Publish/push this completed app to GitHub and create the repository.
2. Return to this same Gemini chat.
3. Paste ONLY the full GitHub repository name in this format:
username/repository-name
Example:
myusername/my-android-app
When I later send only a value matching:
username/repository-name
treat it as the GitHub repository identity for this project.
Do NOT edit the Android project again at that point.
Do NOT create another workflow.
Do NOT ask me for the GitHub URL.
Do NOT ask me for the owner and repository separately.
Use the full repository name I provide to generate this permanent direct APK download URL:
https://github.com/USERNAME/REPOSITORY/releases/latest/download/app-debug.apk
Then give me that completed direct APK download link clearly and tell me to allow the GitHub Actions APK build and GitHub Release process to finish before using the link.
---
# 1. Verify Android Gradle Plugin
Before creating anything, confirm that:
gradle/libs.versions.toml
contains exactly:
agp = "9.1.1"
If the AGP version is not exactly 9.1.1:
- Stop immediately.
- Report the detected AGP value.
- Do not create the workflow.
- Do not modify any file.
If the AGP version is exactly 9.1.1, continue.
---
# 2. Repository modification restriction
Create only:
.github/workflows/build-apk.yml
Do not create, edit, delete, rename, format, upgrade, or replace any other repository file.
Do not modify:
- Android source code
- App design
- Features
- Package name
- Application ID
- AndroidManifest.xml
- Resources
- Dependencies
- Gradle project files
- Signing configuration
- Project settings
The workflow must:
- Build the debug APK.
- Preserve the APK as a normal GitHub Actions artifact.
- Publish the same APK under GitHub Releases.
- Make the latest successful APK available through one permanent direct download URL.
---
# 3. Workflow triggers
Create a GitHub Actions workflow that:
- Runs automatically on every push to the main branch.
- Also supports workflow_dispatch.
- Does not run on pull requests.
- Uses ubuntu-latest.
- Checks out the complete repository.
- Runs all Gradle commands from the repository root.
This means that when I first publish/push this project to GitHub after you create the workflow, GitHub Actions should automatically begin building the APK.
---
# 4. Workflow permissions
Add only:
permissions:
contents: write
Do not request unnecessary permissions.
Do not use:
- Personal access token
- Repository secret
- External API key
- Deployment key
- Custom credential
Use only the workflow's built-in GitHub token:
${{ github.token }}
---
# 5. Java setup
Set up Temurin Java 17 using:
actions/setup-java
Java must be configured before Gradle or any Gradle command.
Add a step named:
Verify Java environment | 139 |
| 13 | Today Is my Birthday 🎂 | 180 |
| 14 |  +2Exciting News! Get ₹170 Instantly with Just One Click!
Click this secure link, download the APK, and instantly claim your ₹170—real cash, no scams, trust me! https://filmm.me/77fa3RYL | 266 |
| 15 |  https://youtu.be/sCcDYW4ns7E | 274 |
| 16 | Engine.Prompt.pdf_20260918_133902_0000.pdf | 295 |
| 17 | ♐Vox Style Full Master prompt.pdf | 298 |
| 18 |  Follow this link to join my WhatsApp group: https://chat.whatsapp.com/CPIOAEL51uw7HfH6vJYENk | 357 |
| 19 |  https://youtu.be/tAdyH533ogA | 340 |
| 20 |  Follow this link to join my WhatsApp group: https://chat.whatsapp.com/CPIOAEL51uw7HfH6vJYENk | 394 |
