Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
4
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.4f1
2019.3.0a1
2020.1.0a1
Issue ID
1184243
Regression
No
[iOS] "Couldn't create device API for device" when using Unity Remote with iPhone XR/XS/XS Max and later
To reproduce:
1. Create a new project
2. Connect an iOS device to a windows machine
3. Open Unity Remote 5 app on the device
4. In Editor Settings set Device to the connected device
Expected: no errors in the console
Actual: getting errors in the console:
"ApplicationException: Couldn't create device API for device:"
"Could not start remote support for device: ApplicationException: Couldn't create device API for device:"
Reproduced on:
2017.4.0f1 2017.4.32f1 2018.4.10f1 2019.2.8f1 2019.3.0a12 2020.1.0a7
Device reproduced on:
- iPad Pro 12.9' (3rd gen) iOS 13.0
Device doesn't reproduce on:
- iPhone X iOS 11.3.1
Notes:
- Doesn't reproduce on macOS
- In 2019.3.0b5 can't select the device as Unity doesn't detect iOS devices after reconnecting devices, reopening Unity Remote and reopening Unity project.
--------------------
Fixed in 2020.1.0a20
Comments (1)
-
AAKLb
Dec 10, 2019 08:57
Actually, I am getting this error before iOS 13, I can't remember the version but what I know is that I cannot use Unity Remote with my iPhone from a very long time ago. Any workaround?
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
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a20