Status Update
Comments
lu...@google.com <lu...@google.com>
je...@google.com <je...@google.com>
am...@google.com <am...@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?
ro...@sentry.io <ro...@sentry.io> #3
I can reproduce the originally reported issue of missing Baseline Profiles with AGP 8.0.0-alpha08.
To verify, check out the
ro...@sentry.io <ro...@sentry.io> #5
Created
am...@google.com <am...@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.
ro...@sentry.io <ro...@sentry.io> #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?
ro...@sentry.io <ro...@sentry.io> #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.
am...@google.com <am...@google.com> #9
It's not working either for me. And I don't have android.experimental.enableNewResourceShrinker.preciseShrinking=true
and tools:shrinkMode='strict'
ro...@sentry.io <ro...@sentry.io> #10
Still happening with AGP 8.0.0-alpha09. Release build apk don't include baseline profile in assets/dexopt/
ke...@gmail.com <ke...@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.
Description
Using the new Instrumentation API, I noticed that sometimes I have the following messages when the instrumentation transforms run (this is just one example of those):
After checking the sources, I found out the warnings are being printed here , which gave me an impression that I cannot actually fix this on my site.
Some background on my instrumentation: I am looking at all classes (so not filtering anything in the
isInstrumentable
method) and then replacing some method calls with my static instrumented method calls. So I'd need those classes to be gone through theFixFramesClassWriter
as well.If there's nothing I can fix on my site, can this at least be an
info
ordebug
level log? It seems it doesn't affect the instrumentation or the runtime behavior of the app, so sounds like this can be avoided to pollute users' console log.Studio Build: N/A Version of Gradle Plugin: 7.2 Version of Gradle: N/A Version of Java: 11 OS: N/A