Fixed
Status Update
No update yet.
Comments
cm...@google.com
je...@google.com
wk...@google.com
This was broken by 3bca759a5ff08352de831bb1e9b61b1ec2b3362d.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
Fix (pending) is I2c2dc7b600603ee430fd0d91b23d52ea8aa29ca9.
wk...@google.com
Almost 2 months later and this is still broken
wk...@google.com
ta...@gmail.com
Since there is no progression, I wanted to share our quick-fix for the issue.
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
#sdkmanager --package_file=${PATH_WORKSPACE}/packages
while read p; do echo "y" | sdkmanager "${p}"; done <${PATH_WORKSPACE}/packages
aa...@gmail.com
jb...@google.com What is the update on this?
aa...@gmail.com
What is the status of this item?
im...@gmail.com
This has been fixed on master today (internal ref: ag/2945015) and will be available in the next SDK release.
Description
I'm trying out the
AndroidComponentsExtension.registerSourceType("my_type")API and was wondering why it registers the following paths automatically (in a module with two flavor dimensions and flavors abc and free):src/main/my_typesrc/free/my_typesrc/abc/my_typesrc/debug/my_typebut it doesn't register, for example:
src/freeAbc/my_typeor
src/freeDebug/my_typeSimilar paths exist by default for java/kotlin sources and any other sources in AGP, as there are configurations created for every permutation of flavors/build types