Status Update
Comments
ju...@google.com <ju...@google.com>
je...@google.com <je...@google.com>
hm...@google.com <hm...@google.com> #2
I have not seen any information about it so just asking here to avoid opening another issue. It also seems that when generating APK with alpha 8 the dex is no more compressed in the APK and stored as is. Leading to way bigger APKs.
While this is not an issue when distributing via Play Store, this could have impact for all the other distribution channels. Is this a normal wanted change and we'll have to deal with it? Or is there some new parameter to control this?
va...@gmail.com <va...@gmail.com> #3
I can reproduce the originally reported issue of missing Baseline Profiles with AGP 8.0.0-alpha08.
To verify, check out the
na...@google.com <na...@google.com> #5
Created
ia...@google.com <ia...@google.com> #6
the location of the baseline profile has changed, it is now in dexopt folder instead of com.android.tools.build.profiles
please file a different bug for other issues so we can assign them correctly for each issue.
gd...@google.com <gd...@google.com> #7
There is no dexopt or any baseline profile related file in the generated aab. There is also nothing related to baseline profile in APK generated with AGP 8.0.
Can you please verify, keep the issue opened and provide a solution?
hm...@google.com <hm...@google.com> #8
As a side note I do use:
android.experimental.enableNewResourceShrinker.preciseShrinking=true
And
<?xml version="1.0" encoding="utf-8"?>
<resources xmlns:tools="http://schemas.android.com/tools"
tools:shrinkMode="strict" />
So maybe depending on when the baseline is packaged it's removed, but in all case it's not working currently so not really WAI.
Description
Coming from https://issuetracker.google.com/issues/244700433 , I changed my build.gradle files to build.gradle.kts and I had the following line:
instead of:
So the android proguard rules weren't loaded which probably caused this.
Would it be possible to warn about this when building using Gradle and potentially throw / fail the build if you're trying to use a proguard file which does not exist?