Search Issue Tracker
Fixed
Fixed in 2023.1.0a20
Votes
1
Found in
2019.4.40f1
2020.3.35f1
2021.3.5f1
2022.1.7f1
2022.2.0a17
2023.1.0a1
Issue ID
UUM-2588
Regression
No
Autoconnect profiler fails to connect when there are two or more Editor instances running
Reproduction steps:
1. Create a new project or open an existing one
2. Open Build settings and change target platform to Android
3. Create a second project or open an existing one
4. Change the target platform to Android
5. Open Build settings (File -> Build Settings)
6. Enable Development Build, Autoconnect Profiler and Deep Profiling
7. Build and run
Expected result: Profiler connects to the build and starts profiling
Actual result: Profiler does not connect to the build
Reproducible with: 2018.4.30f1, 2019.4.17f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0b1
Reproducible on:
VLNQA00321, Xiaomi MI 9 (MI 9), Android 9, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
Does not reproduce on:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 9, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00012, Samsung Galaxy S6 (SM-G920F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
iPhone 12 Pro (iOS 14.2.1)
Not reproducible on:
Windows Standalone
Comments (1)
-
RaveOnTheGrave
Sep 06, 2023 11:54
In Unity 2022.3.8f1 this issue is present
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2023.1.0a20):
Fixed in 2023.1.0a20