Search Issue Tracker
Fixed in 2017.1.0f3
Votes
16
Found in
5.4.2f2
Issue ID
865265
Regression
No
'adb.exe forward' is executed despite build platform set to Standandalone (Windows
In Edit > Preferences > External tools I have my Android SDK + JDK both set
to valid locations, which means Unity is able to run adb.exe if it wants to.
I'm using Windows 10 64bit.
To reproduce:
0. Confirm in the Windows task manager that adb.exe is not running
* If it is, end/quit/kill that task so adb.exe is no longer running
1. In Unity create a new empty/default project
2. Confirm that then build platform is "standalone" (which is the default)
3. Hit CTRL-P to run the empty scene
4. Check the Windows task manager; A moment later you'll see adb.exe
running, which is *not* expected
fixed in
Version 2017.1.0b2 (48952a94fb3b)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
ahmedaniss
Dec 09, 2020 03:28
problem fixed here : http://answers.unity.com/answers/1795579/view.html
Paul_Bronowski
Oct 11, 2018 08:36
Old thread, but something worth adding: If you have the GoogleVR SDK unity asset bundle installed, and you have a GvrControllerInput.cs script in your scene. When you hit play, GoogleVR\Scripts\Controller\Internal\Emulator\EmulatorClientSocket.cs will find adb.exe and launch it, if (serialized field) GvrControllerInput.ConnectionMode == USB or WIFI. You need to set GvrControllerInput.ConnectionMode == OFF when not working with a test device.
fredsa
Mar 04, 2017 21:13
For the `adb` subprocess issue here are a couple of tips:
- You can run `adb kill-server` to get rid of that adb process, although the next time you enter play mode, Unity will spawn a new adb process.
- As a workaround you can run `adb forward tcp:7201 tcp:7201` *before* starting Unity, which makes it so that Steam will no longer consider adb a subprocess (because it's not spawned from Unity editor).
MrLucid72
Mar 04, 2017 07:20
Still annoying, but here's a "Lazy man's workaround" >> https://github.com/Imperium42/killadb
(Still need to click the batch file after every time you close Unity)
MrLucid72
Mar 04, 2017 06:31
(confirmed in 5.5p4)
MrLucid72
Mar 04, 2017 06:31
Confirmed. This is actually a pretty HUGE issue for those that are not aware of this -- for anyone that uses Steamworks.NET (a GREAT majority of people here):
You actually can NEVER exit your Steam app until you reboot!! ....or if you know about the bug, you can end task ADB ... Every. Single. Time. That is incredibly annoying.