Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.2.19f1
2023.1.0a24
2023.2.0a1
Issue ID
UUM-7882
Regression
No
[Profiler] Counters from loaded data not shown in Module Editor when Android device is not connected
How to reproduce:
1. Open the attached project "1417780.zip"
2. Build and Run on Android
3. Open Profiler and select Android device to profile
4. Save current profiling information to a binary file (press button with a floppy disk icon)
5. Disconnect the Android device from computer
6. Load the saved binary file
7. Press on Profiler Modules dropdown menu and press on the cog icon
8. Select any module and press "Add"
9. Inspect Available Counters section
Expected results: User section can be seen
Actual result: User section is not available
Reproducible with: 1.0.0-pre.3 (2021.2.19f1), 1.0.1 (2021.2.19f1, 2022.1.0b15, 2022.2.0a10)
Could not test with: 1.0.0-pre.2 (2021.2.19f1)
Note: expected result appears only when Android device is connected
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case the team is unable to prioritize fixing this bug - but we will be looking into it as a future usability improvement. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.