Status Update
Comments
lu...@google.com <lu...@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?
iu...@google.com <iu...@google.com> #3
I can reproduce the originally reported issue of missing Baseline Profiles with AGP 8.0.0-alpha08.
To verify, check out the
sh...@adobe.com <sh...@adobe.com> #5
Created
am...@zee.com <am...@zee.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.
na...@gtempaccount.com <na...@gtempaccount.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?
lu...@google.com <lu...@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.
sh...@adobe.com <sh...@adobe.com> #9
It's not working either for me. And I don't have android.experimental.enableNewResourceShrinker.preciseShrinking=true
and tools:shrinkMode='strict'
ab...@gmail.com <ab...@gmail.com> #10
ju...@gmail.com <ju...@gmail.com> #11
When they quickly close like that without checking on most part of the tracker anything written after is just plain ignored..
Need to reopen an issue, since no access to proper category hope again that triage put it in the proper place then hope that this time it's properly read.
If only all the parts could be like the R8/D8 part of this issue tracker.
ki...@gmail.com <ki...@gmail.com> #12
Scott, can you have a look if modifying an app according to
lu...@google.com <lu...@google.com> #13
I'm not able to reproduce.
Ben, the link to the repro project from
dh...@gmail.com <dh...@gmail.com> #14
Is there any logs I can provide from the build to help figure out?
Description
To reproduce:
Sample Runtime exception:
The issue is present both the old and new resource shrinkers. So this issue doesn't appear to be related to b/237783271 as that particular issue isn't present in the old resource shrinker.
The resource that is being reported as
android.content.res.Resources$NotFoundException
exists within the APK's resource table and as a file, however the contents are shrunk (empty tag xml file). In the repro case the drawable resource is declared and by an app compat library called by the MainActivity in the app (base module).