Search Issue Tracker
Fixed in 2019.1
Fixed in 2018.2, 2018.3
Votes
15
Found in
2018.3.0a4
2018.3.0a5
Issue ID
1059763
Regression
Yes
Building with Autoconnect Profiler enabled throws error that ShowProfilerWindow could not be called
Steps to reproduce:
1. Create a new project
2. Enable Development build and Autoconnect Profiler
3. Build and Run
Notice error in console:
Couldn't call method ShowProfilerWindow because the class CreateBuiltinWindows or method couldn't be found.
Reproduced with: 2019.1.0a4, 2018.3.0b5, 2018.3.0a8, 2018.3.0a5, 2018.3.0a4, 2018.3.0a11, 2018.2.4f1
Not reproducible: 2018.3.0a3
Environment:
Windows and Mac
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
- [instability] assetBundleVariant YAML parse issue in HDRP package: DebugDisplayLatlong.sha
- Native object references for some object types are always 0 in the memory profiler
- [Android] InputField.onEndEdit is not called when turning off the TouchScreenKeyboard on an Android device
- Acute shadow acne when using two overlapping spotlights
- Raycast made on UI with multiple graphic Raycasters sort strangely when being on the same sorting layer and order
cheesepant
Jan 28, 2019 17:59
This is not a fix. I don't think is fair that someone can mark it as fixed just because is fixed on a newer version. This is just unity workers who want a checklist pass off. Not actually help the community. We can't use anything new because Oculus can't run on any 2018.3 version or newer. So having the window profiler error in older versions make unity obsolete for Quest or any Oculus Program that you want to test. We need these tools.
Yiming075
Dec 20, 2018 08:33
so many bugs!!!!!!!!!!!!!!!!
FeastSC2
Nov 23, 2018 05:54
Is this going to be fixed in Unity v.2018? I don't plan on going to version v.2019.
JMan61
Nov 21, 2018 11:25
Same with 2018.2.16f1 (tested on PS4)
bitepiegames
Nov 01, 2018 07:51
The same with 2018.2.14f1 (tested on OSX)
dandepeched
Oct 24, 2018 09:17
Same issue with 2018.2.13f1