Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
2
Found in
2017.4.0f1
2018.4.0f1
2019.1.2f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1172957
Regression
No
[Mac] Video-heavy project does not get successfully imported when launching the project in batchmode
How to reproduce:
1. Download and extract the linked project
2. Launch it from the terminal using "<UNITY_PATH> -quit -batchmode -projectPath <PROJECT_FOLDER_PATH>"
3. Inspect the Editor.log
Expected results: The assets get imported successfully with no errors
Actual results: After about 40 videos are imported, all the following ones print a "Cannot Open" error to the Editor.log
Reproducible with: 2017.4.32f1, 2018.4.9f1, 2019.2.6f1, 2019.3.0b3, 2020.1.0a4
The full error:
Error Domain=AVFoundationErrorDomain Code=-11829 "Cannot Open" UserInfo={NSLocalizedFailureReason=This media may be damaged., NSLocalizedDescription=Cannot Open, NSUnderlyingError=0x7feb29f06390 {Error Domain=NSOSStatusErrorDomain Code=-12137 "(null)"}}
(Filename: /Users/builduser/buildslave/unity/build/Editor/Src/Video/Media/AVFoundation/AVFoundationVideoMedia.mm Line: 1060)
Comments (1)
-
mcarriere
Dec 09, 2019 14:25
For what it's worth, we have further determined that this issue does not occur either when -batchmode is disabled; as in: running the build with the GUI enabled.
This is definitely undesired for our build server (and isn't possible on Cloud Build), so any progress on this would be greatly appreciated.
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (fix version 2020.2):
Delayed cleanup after importing videos does not get executed early enough when running in batch mode. Changing the execution vehicle for the asynchronous work in this situation will cause the cleanup to happen earlier.
Fixed in 2020.2.0a1.26
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a25.3171
Resolution Note (fix version 2019.3):
Fixed in 2019.3.6f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.23f1