Xamarin-android: Couldn't connect to logcat, GetProcessId returned: 0 when deploying to Oreo Oneplus Device

[JungleJ0n]

Steps to Reproduce

1. New Project, clean & rebuild, debug on phone, debug again
2. 
   
   
   3.
   

No need, create a fresh solution and deploy twice to a OnePlus physical device.

Expected Behavior

App to open every time it's deployed

Actual Behavior

Xamarin happens.

It deploys first time fine and the second time it opens on the device with a white screen and the the app crashes, in VS the following is displayed in VS Output window

Android application is debugging.
Couldn't connect to logcat, GetProcessId returned: 0

This issuse was reported by Simba Mupfunya Here and Acknowledged by dean.ellis Here on 2018-03-21 , and then nothing for over a month, I don't understand how a professional company (backed by MS) allows a problem like this to just sit for a month .

Version Information

[MysteryDash]

Same probleme here.

[caramelopardalis]

In my project, solved by adding x86_64 to Supported architectures of Advanced Android options.

[JungleJ0n]

In my project, solved by adding x86_64 to Supported architectures of Advanced Android options.

I checked the Advance Android Options, and all architectures were all already ticked.

The lack of attention this issue has got despite a developer two months knowing and acknowledging it is "shocking" to say the least.

[Architekt909]

I just got this. I was previously using Visual Studio 2017 15.7.1 and not having any issues connecting to my Samsung S9 physical device. Upon upgrading, today, to 15.7.3, this issue is happening and I can no longer debug on my device.

Edit: I found that disabling "Use Shared Runtime" fixed it. Just disabling "Use Fast Deployment (debug mode only)" didn't help. I had to disable all of it.

Edit 2: I found that after uninstalling my app and doing a clean/rebuild, I was able to put the above settings back and connect again.

[josefromtampa]

I resolved this by factory resetting my Android device. This is using VS2017 15.7.3 for a Pixel XL + Android 8. This might be extreme for some, but I for one don't want to change project settings nor install workaround (because you forget workarounds after they fix them). To reset, use the Android device manager and right-click on your device, then select "Factory Reset".

[MAX-POLKOVNIK]

Factory reset not resolve problem. I used OnePlus 5 Android 8.1.
As said @Architekt909 disabling "Use Shared Runtime" fixes this issue. But this increases build time.

[AshrithaPA]

Facing the same issue on my Oneplus 5 device. On disabling "Use Shared Runtime", I get a build error - "java.exe exited with code 1". Any work around?

[bluekuen]

I also have this issue but with Samsung S7. When disabling "Use Shared Runtime" the issue is fixed but i can't debug anymore. Breakpoints are not hitting anymore.

[Sutphinwb]

This seems like a chronic problem - kind of petty. I started having it after trying the new hyper-v compatible emulator. It was slow, so I switched back to haxm which I upgraded from the Intel site (7.2). That's what we're supposed to do, right? stay current? Now no debug. Some explanation of what the heck it means would be helpful.

[rlasker3]

Luckily for me uninstalling the app from the device and then doing a clean and rebuild got me past this problem.

[jahmai-ca]

Happened to me upgrading from 15.8.1 to 15.8.2. Cleaning out all app/xamarin installs on the device and rebuilding worked around the issue. Now it will debug the app but gets stuck during bootstrap. Why can't I just do a VS upgrade without this nonsense?

[Martinedo]

Uninstalling manualy the app from my phone helped (i kept "Use Shared Runtime" checked). This is happening everytime i upgrade my VS to newer version. In my case its not a big problem, but i can imagine by some apps in a developing process, this can be a pain in the as*.

[hannesganthaler85]

Looks like that this is device specific. On one simulator it worked to debug the app on the other not. For me it helped to uninstall the app from the simulator where the error occur and clean/rebuild it again.

[raquelsa]

Any updates on this?

[Sutphinwb]

The attached device was holding an old instance of the app. Uninstall app
from the phone and try again.

On Tue, Jan 15, 2019, 3:34 PM Raquel Almeida <[email protected]
wrote:

Any updates on this?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/xamarin/xamarin-android/issues/1677#issuecomment-454540927,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfZGGLQul47qE7IeMBHw5mU8MxbiVDRrks5vDjtEgaJpZM4T8yh5
.