Search Issue Tracker

Fixed in 2019.1.X

Fixed in 2018.3.X

Votes

5

Found in

2018.3.0a9

2018.3.0f1

Issue ID

1107874

Regression

Yes

[Windows] Unity Remote 5 doesn't work on iOS because the x86_64 folder is missing from PlaybackEngines\iOSSupport

Themes

-

To reproduce:

1. Start Unity and open and create a New Project
2. Connect iPhone to your machine and start Unity Remote 5 app
3. Press Edit > Project Settings... and select Editor tab
4. In Unity Remote area set Device to Any iOS Device
5. Observe that Console prints Errors:

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)

Notes:
- This issue appears only on Windows
- This issue does not appear macOS
- Workaround: Copy the x86_64 folder from my Unity 2018.2.20f1 folder, paste it to Unity 2018.3.* folder and the issue will vanish

Reproduced on Unity 2018.3.0a9, 2018.3.1f1 and 2019.1.0a12
Not reproduced on Unity 2018.2.20f1 and 2018.3.0a8
Regression on Unity 2018.3.0a9

Comments (12)

  1. dukekamono

    Dec 20, 2018 05:40

    Where is the x86_64 folder located?

  2. pwalders

    Dec 11, 2018 15:35

    Confirmed this fixes the issue. I used Unity 2017.2.5.f1 x86_64 folder for 2018 3.0f1 and indeed, the problem vanished. Make sure you have iTunes running

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.