Android Device Can't Connect With Profiler Window on Unity 2021

Android Device (Android version 12) Can't Connect With Profiler Window on Unity 2021.3.6f1. I restarted Unity Editor and android device couple of times. In build settings Development build and Autoconnect Profiler are enabled. I also updated Unity to version 2021.3.8f1. Also doesn't work. Attaching screenshots.
https://drive.google.com/file/d/1Lee1zhx2lMjczrKvpzbdoAEAZsu2VTVB/view?usp=sharing
https://drive.google.com/file/d/1LffOCWrdrtF6HUVQdJRn93GdDyZqXgk1/view?usp=sharing
https://drive.google.com/file/d/1tUkgBuQt_HoABHKTBd1pf7ZYhVh9h37j/view?usp=sharing

Hi, we recently became aware of this issue. What happens is that when we try to connect from computer to android device we need to set up connection tunnel by using:

adb forward tcp:34999

When we wrote original code we choose extracting of the name for currently running app that we thought is common for android. Our tests on different devices did not uncover any issue, sadly we were just lucky and our recent testing on even bigger group of devices uncovered issues. Turned out that on newer android versions we are calling:

adb forward tcp:34999 Unable to query last resumed application.

Because we cannot query app name. This will be fixed in upcoming changes that should generally improve player connection experience. We have right now a lot of changes targeting android which is one of trickiest of platforms we are supporting. From bad news is that we are right now in phase of testing and it may take a while before it will reach 2021.

For now as a workaround I would recommend using WiFi connection on your phone and use remote target and not local.

1 Like

[quote=“G_Wojo”, post:2, topic: 892122]
Hi, we recently became aware of this issue. What happens is that when we try to connect from computer to android device we need to set up connection tunnel by using:

adb forward tcp:34999

When we wrote original code we choose extracting of the name for currently running app that we thought is common for android. Our tests on different devices did not uncover any issue, sadly we were just lucky and our recent testing on even bigger group of devices uncovered issues. Turned out that on newer android versions we are calling:

adb forward tcp:34999 Unable to query last resumed application.

Because we cannot query app name. This will be fixed in upcoming changes that should generally improve player connection experience. We have right now a lot of changes targeting android which is one of trickiest of platforms we are supporting. From bad news is that we are right now in phase of testing and it may take a while before it will reach 2021.

For now as a workaround I would recommend using WiFi connection on your phone and use remote target and not local.
[/quote]
How I can connect using wifi? I tried to connect via IP address, but I got such an error 8399589--1108938--IP_error.png 8399589--1108938--IP_error.png 8399589--1108938--IP_error.png

[quote=“G_Wojo”, post:2, topic: 892122]
Hi, we recently became aware of this issue. What happens is that when we try to connect from computer to android device we need to set up connection tunnel by using:

adb forward tcp:34999

When we wrote original code we choose extracting of the name for currently running app that we thought is common for android. Our tests on different devices did not uncover any issue, sadly we were just lucky and our recent testing on even bigger group of devices uncovered issues. Turned out that on newer android versions we are calling:

adb forward tcp:34999 Unable to query last resumed application.

Because we cannot query app name. This will be fixed in upcoming changes that should generally improve player connection experience. We have right now a lot of changes targeting android which is one of trickiest of platforms we are supporting. From bad news is that we are right now in phase of testing and it may take a while before it will reach 2021.

For now as a workaround I would recommend using WiFi connection on your phone and use remote target and not local.
[/quote]
Well, I managed it.

I just noticed your reply, great that you managed to figure it out. We are curently in progress of bringing all our player connection connectivity changes to all of supported versions. With a little bit of luck soon this issue and many others should be resolved.

1 Like

[quote=“G_Wojo”, post:5, topic: 892122]
I just noticed your reply, great that you managed to figure it out. We are curently in progress of bringing all our player connection connectivity changes to all of supported versions. With a little bit of luck soon this issue and many others should be resolved.
[/quote]
Actually I managed one time, but further I couldn’t :frowning:

Sorry for the necro but is this a known issue for 2022.3.10f1 as well?

We are on the way bringing even more player connection changes to 2022.3 which should make it almost identical to 2023.3. So right now I'm not 100% sure but soon this should be resolved.