Search Issue Tracker
Fixed in 2.0.1
Votes
0
Found in [Package]
2018.4
2019.4
2020.3
2020.3.1f1
2021.1
2021.2
Issue ID
1330989
Regression
No
Xcode doesn't close after building iOS project via batchmode -runTests command
Reproduction steps:
1. Download "Case_1330989" and open "runtests.sh" located in the Project's directory
2. Replace "{REPLACE:path-to-relevant-Unity.app}" with the local path to the Unity executable
3. Replace "{REPLACE: path-to-Unity-project}" with the local path to the attached Unity project
4. Open the terminal and run "runtests.sh"
5 Observe the process of Unity opening, building to Xcode, opening Simulator and Unity eventually terminating when tests are complete
Expected result: Xcode and Simulator are terminated once the Tests are completed
Actual result: Xcode and Simulator stay open after the Tests are completed
Reproducible with: 2018.4.34f1, 2019.4.24f1, 2020.3.5f1, 2021.1.4f1, 2021.2.0a14 (tested with Xcode 12.4)
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 2.0.1):
Fixed in Test Framework 2.0.1-exp.1