When trying out the example code in google code lab. I create a very simple hello world app with NDK components. Compiling and running on the phone were successful.
However, I couldn't start debugging the native code. When I press the Debug :app icon, the app shows Waiting For Debugger screen, while Android studio got stuck at Starting LLDB Server... .After a few minutes, the console output Failed to connect port.
Neither a real phone nor an emulator can successfully start the debug process.
Updating to Platform-tools version 29.0.4 solves the problem. Apparently, this problem appears in platform-tools 29.0.3
Related
I have just installed an Android Emulator - which is Pixel 4 API 28 - on my Windows 11 computer. I have a project in Expo and I want to test it on Android Emulator. For this, the Expo needs to install Expo Go on Emulator to load my project. By default, it installs automatically when I request for installation by pressing a on my terminal. It detects the connected and available devices on my computer and installs the application.
But for me this does not happen. Instead of installing automatically, the terminal prints me this:
› Opening on Android...
. Learn more: https://expo.fyi/authorize-android-device_4_API_28
This link leads to a 404 page of Github but if I remove the "_4_API_28" part from hyperlink it leads to "Authorize Android Device" page from fyi. This page guides how to reset USB debug permissions of my device to allow my computer to get debug access. I have already did that on my android emulator but nothing changed, it still prints that message.
Is there anything I can do to solve this issue and install Expo Go on my android emulator property?
We have Windows 7 (x64) at work, and I wanted to learn about Xamarin.Forms. Specifically, I wanted to create a very basic app that will eventually run in an iphone and Android.
I installed VS2017 and tried running Build your first Xamarin.Forms App. I get this warning, but click on "Start Anyway":
The emulator pops up, but after a few seconds I get error message qemu-system-i386.exe has stopped working:
I'm new to mobile apps development and Xamarin.Forms (3 days to be exact). With that said, I googled possible solutions, and I found this error message "qemu-system-i386.exe has stopped working" and other questions with similar solutions.
The problem is that the solution requires that I download Android Studio, and I don't want to download anything else until I see something run from VS2017.
I tried running emulator.exe -avd "Android_Accelerated_x86_Oreo" -wipe-data and yet another error:
Finally, I tried installing Hyper-V manager using this Microsoft TechNet link, but I don't have the option Remote Server Administration Tools.
What can I do next? I'm pretty much ready to give up on Xamarin in Windows 7. I still haven't been able to debug an application.
After enabling Intel Virtualization in the BIOS and installing and making sure intelhaxm is running, I opened the project and ran it again.
The "Performance Warning" popup doesn't show up anymore, and there's progress with the android emulator, but it still crashes. This is the screenshot now:
I set up the vcremote correctly(https://msdn.microsoft.com/en-us/library/mt147405.aspx#ConfigureVS) and it connected. I tried to run the default visual studio OpenGLES app on the iphone emulator through vcremote and it built the app just fine, but just as the emulator opened it crashed with the following error:
"Unable to start debugging. Unexpected LLDB output from command "-target-select remote localhost:3031". Command 'target-select'. Fn 'Target select' failed"
I have no idea how to fix this, and it seems that there are not a lot of people running into this problem. Any help would be much appreciated, even if it just helps me understand the error message better, SOMETHING!
I had been struggling with this problem for hours and hours until I found the following link:Remote Debugger Port Assignments
The Visual Studio Remote Debugger can run as an application or as a
background service. When it runs as an application, it uses a port
that is assigned by default as follows: Visual Studio 2022:
4026 Visual Studio 2019:
4024 Visual Studio 2017:
4022 Visual Studio 2015: 4020 Visual Studio 2013: 4018
Visual Studio 2012: 4016
The port 3031 seems to be coming from out of the blue!
I am using Visual Studio 2017 so I used the following command to start up vcremote:vcremote --secure false --nativeDebugProxyPort 4022
After that the iPhone simulator and App started up, but the debugging started to work only after restarting the App during the debug session (which I did by rebooting the iPhone simulator).
I still did not get the pairing working on a secure connection yet :-( Any hints are welcome!
After updating to Android Studio 2.0 my debugger stopped working. When I try to run my app as debug I get stuck waiting for debugger. I can still run app normally.
So there are tons of post on this issue, I've tried everything I could find:
Restart ADB
Restart Android Studio
Restart phone
Restart Computer
Switch USB port
Update everything
Switch develop on/off
Tried with emulator (will also be stuck)
Uninstal Vyzor beta (Chrome plugin that use ADB)
Remove project and load into Android Studio again
Updated JDK 1.7.0_71 to 1.8.0_74
Okay so my application was using android:process=":background" under the application tag. So now with Android Studio 2.0 I had to click "Attach debugger to Android Process" and select the :background process.
This has not been an issue in the past.
If a single activity uses another process then the debugger will also hang at that activity until the debugger is attached to that process (attaching is done manually).
After a fresh installation of Ubuntu 11.10 on my notebook, I'm no longer able to debug any of my projects.
Deploying and starting of my application is working, but every time I try to debug my code the console output looks like this:
Attempting to connect debugger to 'com.vidi.playground' on port 8619
Launch error: Failed to connect to remote VM
And the device or emulator says:
Waiting for Debugger
I tried out everything I found here, including a fresh installation of Eclipse and the SDK.
My workspace is also a new one and I set up a fresh playground project.
I find out that there is a red bug next to my activity in the devices view in Eclipse and in DDMS too. The error occurs on a real device and on the emulator (I've tried different OS versions too).
Here is what I am using (all the newest version):
Ubuntu 11.10
Sun JDK 6
Eclipse Indigo
Android SDK 15
Finally i got the solution for my problem.
The problem is, if you are using a system wide socks-5 proxy, eclipse is trying to reach the debugger through that proxy connection.
Removing this option in my network setting solves the problem for me.