Search Issue Tracker
By Design
Votes
0
Found in
2020.1.0a22
2020.1.0f1
2020.2.0a1
Issue ID
1265910
Regression
No
Crash on RegisterPlugin on opening the project
Reproduction steps:
1. Open the User's supplied project
Reproduces on: 2020.1.0a22, 2020.1.2f1, 2020.2.0a1, 2020.2.0a20
Not reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.0a21
First few lines of the stack trace:
0x00007FF69D04807B (Unity) RegisterPlugin
0x00007FF69D042479 (Unity) FindAndLoadUnityPlugin
0x00007FFEB6B82447 (mono-2.0-bdwgc) [c:\build\output\unity-technologies\mono\mono\metadata\loader.c:1269] mono_lookup_pinvoke_call
0x00007FFEB6B94E76 (mono-2.0-bdwgc) [c:\build\output\unity-technologies\mono\mono\metadata\marshal.c:8035] mono_marshal_get_native_wrapper
0x00007FFEB6C6C0C2 (mono-2.0-bdwgc) [c:\build\output\unity-technologies\mono\mono\mini\method-to-ir.c:8431] mono_method_to_ir
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
- Multiple errors are thrown in the console while using perforce when moving an asset using shortcuts
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
Resolution Note (2020.1.X):
The crash here is in code specific to the project - not in Unity or ARCore SDK code. The issue is that this call needs to be made inside of Start() in ScreenCapturer.cs. It cannot be called in the class constructor before plugins are available.
GoogleARCore.Frame.CameraImage.AcquireCameraImageBytes();
Once that call was moved to Start() the editor crash went away and the app ran on a Pixel 3a without issue.