(Ask Gemini) shows up in logcat without being a link [361535281]

Fixed

Bug

Status Update

No update yet.

Description

er...@hellsoft.se

created issue #1

Aug 22, 2024 05:41PM

```
####################################################

Please provide all of the following information, otherwise we may not be able to route your bug report.

####################################################

1. Describe the bug or issue that you're seeing.
When a fatal crash occurs, the logcat output includes the text "(Ask Gemini)" next to the first line of the exception. This should probably be a link or contain other information. One of my developers asked who Gemini was. :)

2. Attach log files from Android Studio
2A. In the IDE, select the Help..Collect Logs and Diagnostic Data menu option.
2B. Create a diagnostic report and save it to your local computer.
2C. Attach the report to this bug using the Add attachments button.

3. If you know what they are, write the steps to reproduce:

3A. Login to your Google account
3B. Enable Gemini integration
3C. Open logcat and run an app that has a Fatal Exception

Build: AI-241.18034.62.2411.12169540, 202408010925
AS: Koala | 2024.1.1 Patch 2
AI-241.18034.62.2411.12169540, JRE 17.0.11+0-17.0.11b1207.24-11852314x64 JetBrains s.r.o., OS Mac OS X(aarch64) v14.6.1, screens 3024.0x1964.0
Android Gradle Plugin: 8.5.2
Gradle: 8.7
Gradle JDK: JetBrains Runtime 17.0.11 - aarch64
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: 3.29.2
```

Screenshot 2024-08-22 at 19.38.23.png

240 KB

View

Download

DiagnosticsReport20240822-194036.zip

1.6 MB

Download

Comments

rp...@google.com <rp...@google.com> #2Aug 22, 2024 06:00PM

Assigned to aa...@google.com.

Maybe a dup of b/368420773?

vs...@google.com <vs...@google.com> Aug 22, 2024 06:30PM

Reassigned to bl...@google.com.

xa...@google.com <xa...@google.com> #3Aug 22, 2024 06:50PM

Android Gradle Plugin: 8.7.1

Could you try the latest canary, AGP 8.8.0-alpha09?

vs...@google.com <vs...@google.com> #4Sep 1, 2024 03:00PM

Reassigned to sh...@google.com.

I just updated to Android Gradle Plugin: 8.7.2 and the bug is fixed.

er...@gmail.com <er...@gmail.com> #5Sep 1, 2024 04:56PM

I spoke too soon. The bug appears gone when I use a different computer, but that is only because the lint check is disabled on it. The computer with the false positive is a new cloning of my github project which apparently has the lint check enabled. The AGP 8.8.0-alpha09 plugin will not work on ladybug, and I'm too busy to switch to a canary build of android studio just to fix a false positive lint check, sorry.

vs...@google.com <vs...@google.com> #6Sep 1, 2024 05:35PM

I just tried running lint on two more of my computers, one which also has a fresh clone of the github project, and one which has an "ancient" (but up to date) clone of the project -- the two computers have very different Settings -> Editor -> Inspections choices. The old clones do not have this lint check anywhere in their choices, whereas new clones do. Very odd indeed. (I have .idea/ in my .gitignore BTW).

er...@hellsoft.se <er...@hellsoft.se> #7Sep 1, 2024 07:47PM

I understand that it's not trivial to change AGP version; sorry for suggesting that first.

Actually, there is a better way to test: android.experimental.lint.version=8.8.0-alpha09 which will just change the Lint version.

vs...@google.com <vs...@google.com> #8Sep 1, 2024 08:11PM

I decided it was easier to download Android Studio Ladybug Feature Drop | 2024.2.2 Canary 9 than to figure out how to use a different version of lint (a search of stackoverflow suggests this is impossible for what that is worth). Using AGP 8.8.0-alpha09 and gradle-8.10.2-bin.zip on Canary the same error occurs. It looks like it is caused by the K2 compiler mode, because the Inspections options for this lint check does not appear until you enble K2 mode (nor does the false positive error).

sh...@google.com <sh...@google.com> Sep 2, 2024 11:48AM

Accepted by sh...@google.com.

sh...@google.com <sh...@google.com> #9Sep 6, 2024 10:45AM

Marked as fixed.

Thank you for trying the latest canary version of Studio and AGP, I really appreciate that.

I rather confirmed that, with that canary (AGP 8.8.0-alpha09), b/368420773 is really fixed, with the attached reproduction project there. (Note that that issue is also related to K2 mode.)

I also tried altering problematic produceState call with conditional assignment to value, which also works fine. I tried a similar code pattern on compose runtime ProduceStateDetector and its tests, but no luck.

Then... my next guess is whether it is from an old compose runtime, assuming this might be a dup of b/349411310. May I ask which version(s) of Compose runtime (and related libraries) you're using?

an...@google.com <an...@google.com> #10Sep 9, 2024 10:44PM

The compose runtime is from the androidx-compose-bom = "2024.10.01", which is 1.7.5, which is the latest stable version according to its webpage. The project uses libs.versions.toml and gradle assures me that all the versions are up to date (for what that is worth - sometimes I have to manually update versions). I enclose the libs.versions.toml the project uses. The project is my copy of the "Crane" sample app which I have verbosely commented and try to keep up to date with the latest libraries and APIs. The source code involved is in my github repo in the Crane project:

https://github.com/markgray/Composables

The file the false positive is in is:

Crane/app/src/main/java/androidx/compose/samples/crane/details/DetailsActivity.kt