Status Update
Comments
sm...@google.com <sm...@google.com>
yi...@google.com <yi...@google.com>
pe...@google.com <pe...@google.com> #2
Information redacted by Android Beta Feedback.
pe...@google.com <pe...@google.com> #3
From the bug report, we could see that there are no more [Dialer-related logs] and also you have tested the issue in the Dialer version v151, and now v152+ is now available in the Play Store.
So, we request you check the issue in the latest Dialer version and help us with the new bug report and video recording of the issue to investigate further.
While capturing the bug report, please refer to
If the device is not set to Developer mode, Please follow the below path to enable developer options and capture the bug report accordingly.
- Navigate to Settings > Click on About Phone > Click on Software Information > Click 7 times on Build Number continuously. This will allow you to Enable the Developer options
- Navigate to Developer Options and Select Logger sizes per log buffer to maximum available in the device.
- Click on the bug report option and select Full Report and click on Report.
- After a moment, you get a notification that the bug report is ready
- Please share the bug report accordingly.
pe...@google.com <pe...@google.com> #4
Other affected users facing the issue are also welcome to share the bugreport with latest app version to take it forward.
de...@google.com <de...@google.com> #5
Please provide the requested information in
From the bug report, we could see that there are no more [Dialer-related logs] and also you have tested the issue in the Dialer version v151, and now v152+ is now available in the Play Store.
So, we request you check the issue in the latest Dialer version and help us with the new bug report and video recording of the issue to investigate further.
While capturing the bug report, please refer to
https://developer.android.com/studio/debug/bug-report#bugreportdevice . Following instructions are for your quick reference.
If the device is not set to Developer mode, Please follow the below path to enable developer options and capture the bug report accordingly.
- Navigate to Settings > Click on About Phone > Click on Software Information > Click 7 times on Build Number continuously. This will allow you to Enable the Developer options
- Navigate to Developer Options and Select Logger sizes per log buffer to maximum available in the device.
- Click on the bug report option and select Full Report and click on Report.
- After a moment, you get a notification that the bug report is ready
- Please share the bug report accordingly.
go...@gmail.com <go...@gmail.com> #6
Thank you for reporting this issue. We have a fix rolling out now.
pe...@google.com <pe...@google.com> #7
This will be fixed in patch 3 of BB.
ra...@gmail.com <ra...@gmail.com> #8
There was 1 root cause:
java.lang.NullPointerException(wrapped.contentEncoding must not be null)
call GlideException#logRootCauses(String) for more detail
Cause (1 of 1): class java.lang.NullPointerException: wrapped.contentEncoding must not be null
pi...@gmail.com <pi...@gmail.com> #9
com.android.tools.idea.kotlin.UninitializedPropertyAccessException: lateinit property interceptedResponse has not been initialized
at com.android.tools.appinspection.network.httpurl.TrackedHttpURLConnection.getHeaderFields(TrackedHttpURLConnection.kt:336)
at com.android.tools.appinspection.network.httpurl.HttpsURLConnectionWrapper.getHeaderFields(HttpsURLConnectionWrapper.kt:189)
at com.amazonaws.http.UrlHttpClient.createHttpResponse(UrlHttpClient.java:111)
at com.amazonaws.http.UrlHttpClient.execute(UrlHttpClient.java:85)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:386)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:229)
at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4829)
at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1912)
at com.amazonaws.mobileconnectors.s3.transferutility.UploadTask.uploadSinglePartAndWaitForCompletion(UploadTask.java:282)
at com.amazonaws.mobileconnectors.s3.transferutility.UploadTask.call(UploadTask.java:114)
at com.amazonaws.mobileconnectors.s3.transferutility.UploadTask.call(UploadTask.java:59)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at java.lang.Thread.run(Thread.java:1012)
Is this related? Unfortunately I don't have the permissions to create a new issue.
pe...@google.com <pe...@google.com> #10
Which version of Studio are you using?
ea...@gmail.com <ea...@gmail.com> #11
Same issue for me, lateinit property interceptedResponse has not been initialized
. I'm using this version: Android Studio Dolphin | 2021.3.1 RC 1.
pe...@google.com <pe...@google.com> #12
The lateinit exception is fixed in Giraffe.
ru...@kavak.com <ru...@kavak.com> #13
hello, I have Android Studio Dolphin | 2021.3.1 Patch 1 and I'm getting the same error with
lateinit property interceptedResponse has not been initialized
pe...@google.com <pe...@google.com> #14
Hi Ruben, unfortunately the fix is only addressed in Giraffe. Please upgrade to it if it's possible.
d....@gmail.com <d....@gmail.com> #15
"failed with exception: com.android.tools.idea.kotlin.UninitializedPropertyAccessException: lateinit property interceptedResponse has not been initialize"
Android Studio Flamingo | 2022.2.1 Beta 1
Build #AI-222.4459.24.2221.9471578, built on January 10, 2023
pe...@google.com <pe...@google.com> #16
Would you able to share the stack trace?
pb...@gmail.com <pb...@gmail.com> #17
Android Studio Electric Eel | 2022.1.1 Build #AI-221.6008.13.2211.9477386, built on January 11, 2023
FATAL EXCEPTION: FirebaseStorage-Upload-4
com.android.tools.idea.kotlin.UninitializedPropertyAccessException: lateinit property interceptedResponse has not been initialized
at com.android.tools.appinspection.network.httpurl.TrackedHttpURLConnection.getHeaderFields(TrackedHttpURLConnection.kt:337)
at com.android.tools.appinspection.network.httpurl.HttpURLConnectionWrapper.getHeaderFields(HttpURLConnectionWrapper.kt:149)
at com.google.firebase.storage.network.NetworkRequest.parseResponse(NetworkRequest.java:418)
at com.google.firebase.storage.network.NetworkRequest.performRequestStart(NetworkRequest.java:250)
at com.google.firebase.storage.network.NetworkRequest.performRequest(NetworkRequest.java:270)
at com.google.firebase.storage.network.NetworkRequest.performRequest(NetworkRequest.java:289)
at com.google.firebase.storage.UploadTask.send(UploadTask.java:518)
at com.google.firebase.storage.UploadTask.delaySend(UploadTask.java:451)
at com.google.firebase.storage.UploadTask.uploadChunk(UploadTask.java:477)
at com.google.firebase.storage.UploadTask.run(UploadTask.java:247)
at com.google.firebase.storage.StorageTask.lambda$getRunnable$7$com-google-firebase-storage-StorageTask(StorageTask.java:1072)
at com.google.firebase.storage.StorageTask$$ExternalSyntheticLambda7.run(Unknown Source:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
pa...@altametrics.com <pa...@altametrics.com> #18
ja...@gmail.com <ja...@gmail.com> #19
I am using the latest stable version of Android Studio and still facing the same issue! Please help!
Error Information:
com.android.tools.idea.kotlin.UninitializedPropertyAccessException: lateinit property interceptedResponse has not been initialized
at com.android.tools.appinspection.network.httpurl.TrackedHttpURLConnection.getHeaderFields(TrackedHttpURLConnection.kt:337)
at com.android.tools.appinspection.network.httpurl.HttpURLConnectionWrapper.getHeaderFields(HttpURLConnectionWrapper.kt:149)
...
...
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
...
...
at java.lang.Thread.run(Thread.java:923)
Android Studio Information:
Android Studio Electric Eel | 2022.1.1 Patch 1
Build #AI-221.6008.13.2211.9514443, built on January 21, 2023
Runtime version: 11.0.15+0-b2043.56-8887301 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.15.0-58-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 12
Registry:
external.system.auto.import.disabled=true
ide.text.editor.with.preview.show.floating.toolbar=false
Non-Bundled Plugins:
com.dubreuia (2.3.0)
EclipseCodeFormatter (22.0.203.000.0-Eclipse_2021-09)
Current Desktop: ubuntu:GNOME
pe...@google.com <pe...@google.com> #20
Correction to
pe...@google.com <pe...@google.com> #21
The fix has been cherry picked into F beta 3 which will release next week Feb 14.
Description
Build: AI-211.7628.21.2111.8139111, 202202012023,
AI-211.7628.21.2111.8139111, JRE 11.0.11+9-b60-7590822x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 3200.0x1800.0
AS: Bumblebee | 2021.1.1 Patch 1; Kotlin plugin: 211-1.6.10-release-923-AS7442.40; Android Gradle Plugin: 7.1.1; Gradle: 7.3.3; Gradle JDK: version 11.0.12; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: LLDB 3.1 (revision: 3.1.4508709); CMake: from local.properties: (not specified), latest from SDK: 3.18.1-g262b901-dirty, from PATH: (not found)
I enable network profiler (https://developer.android.com/studio/profile/network-profiler )
HttpURLConnection gets wrapped in TrackedHttpURLConnection (com.android.tools.appinspection.network.httpurl.TrackedHttpURLConnection)
I call
con.getHeaderField("Content-Type")
The method contract is "Returns: the value of the named header field, or null if there is no such field in the header."
However,
TrackedHttpURLConnection
crashes in this call with:java.lang.NullPointerException: wrapped.getHeaderField(key) must not be null
It seems that your injected TrackedHttpURLConnection breaks the contract by expecting non-null result from wrapped HttpURLConnection.
Expected fix: return null in your TrackedHttpURLConnection.getHeaderField if there's no such header field.