skip export fails to export APK/AAB for flavored Android app outputs
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 3.2k
- Forks
- 106
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 1
Description
Issue:
Running skip export on an Android build with flavors successfully generates the .apks but errors saying they are unable to be found.
build.gradle.kts:
...
android {
flavorDimensions += "env"
...
productFlavors {
create("dev") { dimension = "env" }
create("prod") { dimension = "env" }
}
}
...
Actual Android outputs
Gradle produces flavored artifacts like:
.build/Android/app/outputs/apk/dev/debug/app-dev-debug.apk
.build/Android/app/outputs/apk/prod/debug/app-prod-debug.apk
.build/Android/app/outputs/bundle/devDebug/app-dev-debug.aab
.build/Android/app/outputs/bundle/prodDebug/app-prod-debug.aab
Expected behavior
skip export should either:
- detect flavored outputs and export the generated APK/AAB correctly
- provide a way to select which flavor to export
- avoid treating this as a failure when the Android build itself succeeded
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the Android handling used by skip export and compare its lookup with the flavored output paths listed in the issue. Done means skip export can locate and export the generated APK/AAB for flavored builds, or clearly reports how a flavor is selected, without failing after a successful Android build.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, swift
- Domain
- build-system, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100