Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
1
Found in
2017.4.0f1
2019.2.0a7
Issue ID
1133479
Regression
No
[iOS] Built Player fails to connect to Profiler when using iPhone XR, iPhone XS or iPhone XS Max
To reproduce:
1. Start Unity and open and create a New Project
2. Switch Platform to iOS
3. Press File > Build Settings...
4. Check "Development Build" and "Autoconnect Profiler" checkboxes
5. Build for iOS
6. Deploy the Xcode project to iPhone XR, iPhone XS or iPhone XS Max
Expected results: Built Player connects to Profiler
Actual results: Built Player fails to connect to Profiler
Notes:
- If You try to manually connect iPhone XR, iPhone XS or iPhone XS Max to Profiler, it is also fails
Tested with:
- iPhone 7 Plus, iOS: 12.0 - Not Reproduced
- iPhone X, iOS: 11.3.1 - Not Reproduced
- iPhone XR, iOS: 12.0 - Reproduced
- iPhone XS, iOS: 12.0 - Reproduced
- iPhone XS Max, iOS: 12.0 - Reproduced
Reproduced on Unity 2017.4.0f1, 2017.4.22f1, 2018.3.8f1, 2019.1.0b6, 2019.2.0b5 and 2019.3.0a5
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
- Source Generation with GeneratePropertyBag fails when using reserved keywords as variable names with @ prefix
- Prismatic ArticulationBody moves in opposite direction when using targetVelocity
- Shader Graph skybox material is rendered inccorrectly in builds when "Allow Material Override" or "Cast Shadows" are enabled and the "Deferred" Rendering Path is used
- Object motion is affected by incorrectly added rotation motion when importing animations
- Base class's Context Menu method is called when calling it in the Editor from the child class and the child class overrides this method
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a20