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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a20