Obsolete
Status Update
Comments
lb...@gmail.com <lb...@gmail.com> #2
Maybe between step 2 and step 3 I had the app crash, due to multiple orientation changes.
lb...@gmail.com <lb...@gmail.com> #3
BTW, what you see on the video is not an emulator. It's the device. I used this:
https://github.com/Genymobile/scrcpy
dn...@google.com <dn...@google.com>
dn...@google.com <dn...@google.com> #4
Thank you for reporting this issue.
We are not able to reproduce this issue.
If you debug the app , then only you will get that dialog which you have mentioned in comment #1 .
If you directly run the app, app is running successfully.
Attached video for reference.
We are not clear about the steps.
Please clarify the issue.
We are not able to reproduce this issue.
If you debug the app , then only you will get that dialog which you have mentioned in
If you directly run the app, app is running successfully.
Attached video for reference.
We are not clear about the steps.
Please clarify the issue.
lb...@gmail.com <lb...@gmail.com> #5
@4 You forgot what I wrote later, that you need to cause it to crash by changing orientation.
Attached video.
I think I can reproduce it all the time now.
Attached video.
I think I can reproduce it all the time now.
dn...@google.com <dn...@google.com> #6
We have passed this to the development team and will update this issue with more information as it becomes available.
dn...@google.com <dn...@google.com> #7
We've deferred this issue for consideration in a future release. Thank you for your time to make Android better.
dn...@google.com <dn...@google.com> #8
In case you want to provide more information with respect to this bug, please file a bug in AOSP via "https://goo.gl/TbMiIO ".
is...@google.com <is...@google.com>
cc...@google.com <cc...@google.com>
sa...@google.com <sa...@google.com> #9
We will be closing this bug due to being logged in a Preview version of Android. If the issue is still relevant and reproducible in the latest public release (Android Q), please capture a bugreport and log the bug in https://goo.gl/TbMiIO . If a reply is not received within the next 14 days, this issue will be closed. Thank you for your understanding.
Description
Build #AI-181.5281.24.32.4860949, built on June 26, 2018
JRE: 1.8.0_152-release-1136-b04 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
* Which Developer Preview build are you using? See Settings > About phone > Build number (for example OPP5.170921.005).
PPP3.180510.008
* Is this a regression from O to P?
Not sure
* What device are you using? (for example, Pixel XL)
Pixel 2
* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Not sure how I got to this.
Maybe as such:
1. import attached project.
2. run app.
3. put breakpoint and choose to debug
4. disable instant run
5. run app.
* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Framework
* What was the expected result?
Since I've chosen to do a simple run, without debugging, it shouldn't wait
* Can you provide the API document where this expected behavior is explained?
No
* What was the actual result?
It keeps on waiting for the debugger, even though I didn't tell it to.
This even occurs when I remove the app and try again.
Attached bug report, video, and IDE log.