Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.1.0f2
Issue ID
1149188
Regression
Yes
[Android] TestRunner does not recognize a crash when running tests on Android devices
Steps to reproduce:
- Install Unity Editor version 2019.1.0f2 with Android support
- Open the project contained in ParticleCrashTestRunnerRepro.zip - attached below.
- Set up a Samsung Android device that can run GearVR, such as a Samsung S9
- Set up the osig file for your device: https://dashboard.oculus.com/tools/osig-generator/
- From the command line, run the command "adb uninstall com.UnityTestRunner.UnityTestRunner"
- Replace [PathToEditor] and [PathToFolderContainingProject] in the command below, then from the command line execute:
`
[PathToEditor]\Unity.exe -runTests -projectPath [PathToFolderContainingProject]\ParticleCrashTestRunnerRepro -testPlatform Android -testResults C:\Users\jackpr\ParticlesTest\TestResults.xml -logfile C:\Users\jackpr\ParticlesTest\UnityLog.txt
`
Expected:
- The editor launches, it builds the test project, and deploys the test project to the device.
- The test fails, and the player crashes
- Unity Editor recognizes that the player crashed through a timeout or some other method. The test reports as failed.
Observed:
After the player quits as a result of https://fogbugz.unity3d.com/f/cases/1145324/, the editor instance just sits there. It does not time out.
Note: the symptom that causes this behavior has been fixed, so it will not be reproducable through this method in later versions of the editor.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment