Fixed
Status Update
No update yet.
Comments
rm...@google.com
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue? Are you also using 2 phones: Pixel 4 with Android 10 and Sony Xperia L3?
Steps to reproduce
What steps are needed to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
Screen record of the issue, if possible
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.
Android build
Which Android build are you using? (e.g. PPP5.180610.010)
Device used -- Device Make, Model, Android OS Version
Which device did you use to reproduce this issue? Are you also using 2 phones: Pixel 4 with Android 10 and Sony Xperia L3?
Steps to reproduce
What steps are needed to reproduce this issue?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Screen record of the issue, if possible
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Note: Please avoid uploading directly to the issue using attachments. Please upload to google drive and share the folder to android-bugreport@google.com, then share the link here.
ni...@google.com
ic...@google.com
It's bug in you Bluetooth stack. It's not depend on any build system. I point exact line in code where bug happen. Please stop use blueprint response.
This problem happened even in system applications.
Current happened on Pixel 6 device whit last march update. Also this bug present in gabeldorsche Bluetooth stack
Description
AI-191.7479.19.36.5679705, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1600x900, 1920x1080
AS: 3.6 Canary 4; Kotlin plugin: 1.3.40-release-Studio3.5-1; Android Gradle Plugin: 3.6.0-alpha04; Gradle: 5.4.1; NDK: from local.properties: (not specified), latest from SDK: (not found); LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
IMPORTANT: Please read
---
This is related to this issue:
'androidx.constraintlayout:constraintlayout:2.0.0-beta2' breaks AS 3.6C4
causing resource link errors concerning Flow artifacts.
following result on drilling down the cause by checking alphas ande betas to
the 'androidx.constraintlayout:constraintlayout:2.0.0-xxx' dependecy
where "xxx" is:
"beta2": Fail
"beta1": Fail
"alpha5": Fail
"alpha4": Fail
"alpha3": OK
To let AS3.6C4 to continue compiling with 'androidx.constraintlayout:constraintlayout:2.0.0-xxx'
You should change dependency to
'androidx.constraintlayout:constraintlayout:2.0.0-alpha3'
but you may loose the latest functions such as 'flow' in constraintlayouts.
Otherwise you need to downgrade to (or reinstall) AS3.6C3.
RG