Sometimes app starts and displays 'Waiting for debugger' even if it was not launched in debug mode [146010811]

Assigned

Bug

Reviewed (L1)

Status Update

No update yet.

Description

fl...@gmail.com

created issue #1

Dec 11, 2019 05:09PM

It happens also if I try to profile the app. The app is built in release mode but with the debuggable and jniDebuggable flags set to true and minify false.
Other times the doesn't start at all after the 'Install' phase.
The idea.log file attached is from an attempt to start the app without debugging (i.e. Shift+10). Device is a Pixel 4.

Thanks.

Regards,
Flavio Antonioli.

Build: AI-191.8026.42.35.6010548, 201911150702, AI-191.8026.42.35.6010548, JRE 1.8.0_202-release-1483-b49-5587405x64 JetBrains s.r.o, OS Linux(amd64) v4.15.0-72-generic, screens 3840x2160, 1600x1200AS: 3.5.3; Android Gradle Plugin: 3.5.3; Gradle: 5.4.1; NDK: from local.properties: 20.0.5594570, latest from SDK: 20.0.5594570; LLDB: LLDB 3.1 (revision: 3.1.4508709); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: 3.10.2Source: user_sentiment_feedback IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

idea.log

614 KB

View

Download

Comments

vi...@google.com <vi...@google.com> #2Dec 12, 2019 12:00PM

Assigned to rp...@google.com.

Submitter:

Can you please provide a brief text explanation of:

What is the summary of the issue you're seeing
What is the expected behavior
What is the actual behavior
What software is showing the bug. What version of software are you reporting it against
What operating system are you running (android version, device)
If an app integration, what version of emojicompat or emoji2 are you linking against.

Thanks!

es...@google.com <es...@google.com> Apr 30, 2020 11:11PM

Reassigned to an...@google.com.

ju...@google.com <ju...@google.com> Mar 2, 2022 12:41AM

Status: New

ac...@google.com <ac...@google.com> #3Mar 10, 2022 07:41AM

Log has a whole bunch message related to this:

2019-12-11 18:02:46,747 [5-thread-1] INFO - ansport.TransportDeviceManager - [Transport]: connect error: Connection refused

May be it has something to do with inspector?

di...@google.com <di...@google.com> Mar 10, 2022 09:36AM

Assigned to ps...@google.com.

jb...@google.com <jb...@google.com> #4Mar 10, 2022 06:09PM

Reassigned to du...@google.com.

I don't think this is related to inspectors, and I'm pretty sure the lines seen in the log are another symptom of the same problem, not the cause. I say deployment is the right place, maybe?

du...@google.com <du...@google.com> #5Oct 5, 2024 03:35AM

Reassigned to sa...@google.com.

Hi, is this still happening?