(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.

Looks like ContextWrapper.getClassLoader() is throwing an NPE.

java_vm_ext.cc:591] JNI DETECTED ERROR IN APPLICATION: JNI FindClass called with pending exception java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.ClassLoader android.content.Context.getClassLoader()' on a null object reference
java_vm_ext.cc:591]   at java.lang.ClassLoader android.content.ContextWrapper.getClassLoader() (ContextWrapper.java:176)
java_vm_ext.cc:591]   at java.lang.ClassLoader com.android.tools.agent.app.inspection.AppInspectionService.findClassLoader() (AppInspectionService.java:435)
java_vm_ext.cc:591]   at void com.android.tools.agent.app.inspection.AppInspectionService.<init>(long) (AppInspectionService.java:88)
java_vm_ext.cc:591]   at com.android.tools.agent.app.inspection.AppInspectionService com.android.tools.agent.app.inspection.AppInspectionService.createAppInspectionService() (AppInspectionService.java:-2)
java_vm_ext.cc:591]   at com.android.tools.agent.app.inspection.AppInspectionService com.android.tools.agent.app.inspection.AppInspectionService.instance() (AppInspectionService.java:55)
java_vm_ext.cc:591] 
java_vm_ext.cc:591]     in call to FindClass

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

I added NPE protection that resorts to a "safe" way to get a classloader.

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

Reassigned to sh...@google.com.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Ladybug Feature Drop | 2024.2.2 Canary 2
Android Gradle Plugin 8.8.0-alpha02

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

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

I can confirm App inspection works. Thank you for fixing this.

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

We often share logcat output in bugreports and such. This is noise we can do without.

Just want to confirm: you are copying logcat output from the logcat pane in Studio in your bugreports? (These aren't added to the real adb logcat output, they are only shown inside Studio, so they won't be in any automated bug report systems)

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

Yes, that happens when developers are registering bugs, or adding more data to bugs detected in QA or Crashlytics.

This is a common practice at several teams I worked in, so it's not unique to my current workplace.

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

Sounds good. Adding a setting is tracked in b/363791805. This bug will focus on fixing the original issue.

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.

http://ag/29090651 fixes the issue. Should be available in the next canary release.

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