Search Issue Tracker
By Design
Votes
0
Found in
5.6.0f3
Issue ID
917337
Regression
Yes
[WSA] Activer Profiler does not profile the UWP build on a remote device
Steps to reproduce:
1. Create a new project
2. Switch platform to Windows Store
3. Build for WSA Universal 10 (.NET backend), Enable C# projects
4. Open Visual Studio solution
5. Deploy on a device
6. Open Profiler Window
7. Select WindowsPlayer in Connect Player (or Active Profiler for 5.6 and below)
8. Observe that the Profiler does not connect to a device
Expected result: You should be able to connect to a device via Active Profiler
Actual result: You are unable to connect to a device via Active Profiler
Note:
With 5.6.0f3 a device does not appear in the drop-down for "Active Profiler" within the Unity Profiler
Reproduced with: 5.6.0f3, 5.6.1p3, 2017.1.0b8
Not reproduced with: 5.5.4f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][IL2CPP] Player crashes on __memcpy_aarch64_simd+276 when invoking native code via a plugin on some ARM64 Android devices
- [Android]Resources fail to load when the AAB build contains a large Addressables Bundle
- Unity is loading internal version of SharpZipLib instead of local version
- The Context Menu items are ordered incorrectly
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
Add comment