Fixed
Status Update
Comments
lu...@google.com <lu...@google.com>
je...@google.com <je...@google.com>
am...@google.com <am...@google.com> #2
Is this fixed? I'm still seeing this issue with AGP 8.1.0-beta01 + Gradle 8.1
ro...@sentry.io <ro...@sentry.io> #3
The fix has not been landed.
am...@google.com <am...@google.com> #4
Due to this bug in CI we hit configuration cache invalidation 100% of the time. Can we make sure the fix lands soon? And especially before 8.1.0 stable.
ro...@sentry.io <ro...@sentry.io> #5
I cc'ed you on the CL which should be landed this week.
am...@google.com <am...@google.com> #6
Aurimas, is this 8.1 blocking for Androidx? If not, feel free to remove the "Blocking release" label.
ro...@sentry.io <ro...@sentry.io> #7
ro...@sentry.io <ro...@sentry.io> #10
Scott, do we have a cherry-pick ready for the lint fix?
ke...@gmail.com <ke...@gmail.com> #11
Yes, Change-Id: I994677cebb63de5472bb8ea561bdad0336c72f55
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