You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My project has a few flavors. Each flavor has its own app ID.
I wanted to publish pre-built APKs per each flavor. After reading the documentation section about Uploading a pre-existing artifact I understood that I need to execute the following command per each flavor's apk: ./gradlew publishApk --artifact-dir path/to/flavor/apk
But executing the command above actually tried to publish that specific apk to all flavors!
I could see that the flavor specific publishing task, i.e. publishApkFlavorBuildType, was executed where the first one which matched the app ID of the provided apk was successful while the rest obviously failed.
I decided to try specifying the flavor specific publishApk task with --artifact-dir option, e.g.: ./gradlew publishApkFlavorBuildType --artifact-dir path/to/flavor/apk and 🎉 it worked!
I'm not sure if this is by design or a bug. If it's by design, please make the documentation clearer regarding flavor publishing.
Thank you for your awesome work! 😄
The text was updated successfully, but these errors were encountered:
Nimrodda
added
the
docs
Indicates issues where the documentation should be changed or enhanced
label
Aug 9, 2019
Right, I would say that's expected since publishApk is a lifecycle task and doesn't actually do anything. However, I think it makes sense to try and parse a prebuild APK, check its package, and noop if the current build variant doesn't match.
SUPERCILEX
added
bug
Indicates an unexpected problem or unintended behavior
feature:apk
Involves APKs
feature:bundle
Involves app bundles
and removed
docs
Indicates issues where the documentation should be changed or enhanced
labels
Aug 9, 2019
SUPERCILEX
changed the title
Uploading pre-built apk documentation doesn't take flavors into account
Noop if prebuild artifact's package doesn't match current variant
Aug 9, 2019
My project has a few flavors. Each flavor has its own app ID.
I wanted to publish pre-built APKs per each flavor. After reading the documentation section about Uploading a pre-existing artifact I understood that I need to execute the following command per each flavor's apk:
./gradlew publishApk --artifact-dir path/to/flavor/apk
But executing the command above actually tried to publish that specific apk to all flavors!
I could see that the flavor specific publishing task, i.e.
publishApkFlavorBuildType
, was executed where the first one which matched the app ID of the provided apk was successful while the rest obviously failed.I decided to try specifying the flavor specific
publishApk
task with--artifact-dir
option, e.g.:./gradlew publishApkFlavorBuildType --artifact-dir path/to/flavor/apk
and 🎉 it worked!I'm not sure if this is by design or a bug. If it's by design, please make the documentation clearer regarding flavor publishing.
Thank you for your awesome work! 😄
The text was updated successfully, but these errors were encountered: