Unity Remote 5 NOT working with 2018.3.0f2

Target Platforms Mobile
1

I just upgraded to Unity 2018.3.0f2, from 2018.2.18f1.

Before Unity Remote 5, which I was running on an iPad Mini 2 via the USB port was working flawlessly. NOW it does NOT work at all.

When I am running Unity and plug in my iPad Mini 2, I get the following error messages:

EntryPointNotFoundException: StartIosProxy
UnityEditor.iOS.iOSDevice.StartIosProxy (System.UInt16 devicePort) (at C:/buildslave/unity/build/PlatformDependent/iPhonePlayer/Extensions/Common/iOSDevice.cs:46)
UnityEditor.iOS.iOSDevice.StartRemoteSupport () (at C:/buildslave/unity/build/PlatformDependent/iPhonePlayer/Extensions/Common/iOSDevice.cs:54)
UnityEditor.IDeviceUtils.StartRemoteSupport (System.String deviceId) (at C:/buildslave/unity/build/Editor/Mono/Utils/IDeviceUtils.cs:14)

Could not start remote support for device: EntryPointNotFoundException: StartIosProxy
UnityEditor.iOS.iOSDevice.StartIosProxy (System.UInt16 devicePort) (at C:/buildslave/unity/build/PlatformDependent/iPhonePlayer/Extensions/Common/iOSDevice.cs:46)
UnityEditor.iOS.iOSDevice.StartRemoteSupport () (at C:/buildslave/unity/build/PlatformDependent/iPhonePlayer/Extensions/Common/iOSDevice.cs:54)
UnityEditor.IDeviceUtils.StartRemoteSupport (System.String deviceId) (at C:/buildslave/unity/build/Editor/Mono/Utils/IDeviceUtils.cs:14)

2

It seems to be also not working with Android Devices.

3

And I have the exact same error with my iPad. But this workaround worked!

You can copy this from any older version of Unity.

“you can go to your Unity install folder and copy editor\Data\PlaybackEngines\iOSSupport\x86_64*.* one level up into iOSSupport folder. This is for 64bits, for 32bits replace x86_64 with just x86. The native library will load then and those errors should go away.”

4

Workaround for Android, when not working :

Setup in Unity: “Unity Remote Editor Settings> Device> Any Android Device”

Then:

  • Open a command window.

  • Navigate to your Android ADB folder. (For Windows Users, C:\Users[UserName]\AppData\Local\Android\sdk\platform-tools)

  • Kill the adb server with the following command: adb kill-server

  • Restart the adb server: adb start-server

  • Open Unity Remote on your device.

  • Press play.

Repeat whenever you encounter this issue.

5

I got the same issue after upgrading from 2018.3.0f1 to 2018.3.0f2.

This is a section from the editor log after starting play mode with an Android device attached (recognized in build settings):

6

Any one fixed the issue for IOS?? in 2018.3.0f2 is not working and not in the new 2019.1.0a12 (so even in 2019 it’s not fixed).

7

Still dont working :frowning:

8

Got the same issue. Now fixed with 2018.3.12f

9

not fixed on 2019.1, android debug is on, tried restart editor, but no response from Remote 5

10

Having the same problem. But I don’t even have a X86 folder in there. What to do then?

“you can go to your Unity install folder and copy editor\Data\PlaybackEngines\iOSSupport\x86_64*.* one level up into iOSSupport folder. This is for 64bits, for 32bits replace x86_64 with just x86. The native library will load then and those errors should go away.”