Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stuck at waiting for application... #94

Open
felixlix45 opened this issue Apr 4, 2023 · 5 comments
Open

Stuck at waiting for application... #94

felixlix45 opened this issue Apr 4, 2023 · 5 comments

Comments

@felixlix45
Copy link

Using the latest release, got stuck when start a new trace. Need some insight

  • Android Studio is closed
  • Activity Name filled or not filled (same result)

Macbook Pro M1

@Grigory-Rylov
Copy link
Owner

Thanks for reporting! Was it an app or a plugin? Is application debuggable (or release with rooted device) ?

@esafirm
Copy link

esafirm commented Jun 7, 2023

I also have a similar but not the same situation. In my case, opening the app manually works.

Machine: 2018 Intel MBP
Android App: Debuggable on a non-rooted phone
YAMP: Latest 23.01.17, standalone

@Grigory-Rylov
Copy link
Owner

Hello, are you using correct main activity name? YAMP just trying to start that activity with ADB command like 'adb shell am start -n yourpackagename/.activityname' . Please try to execute that command in terminal with your package and activity name - will activity start?

@esafirm
Copy link

esafirm commented Jun 8, 2023

Hello, are you using correct main activity name? YAMP just trying to start that activity with ADB command like 'adb shell am start -n yourpackagename/.activityname' . Please try to execute that command in terminal with your package and activity name - will activity start?

You're right, I got the wrong Activity name. Checking the log it was a SecurityExcepiton because exported=false.
Maybe we can have a better error message for this?

Now the issue is shifting, the application opened but I got Cannot find process <package name> message again

Now the log shows this error:

om.github.grishberg.tracerecorder.exceptions.AppTimeoutException: <package_name> not started

@Grigory-Rylov
Copy link
Owner

You're right, I got the wrong Activity name. Checking the log it was a SecurityExcepiton because exported=false.
Maybe we can have a better error message for this?

 Good idea!

Cannot find process

Is the android studio currently running ? Android Studio holds debug port and other applications can't see debug process.
You can use YAMP as the plugin. Thus YAMP will reuse AS's debug port. Or you can kill android studio and try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants