CLI batchMode breaks when Smart-Inspector is in the project
See original GitHub issueThis is a weird one so I’ve no idea what it could be about but I’m throwing it out there because it’s a deal breaker for us since it breaks our CI pipeline.
After adding Smart-Inspector to the project we can no longer run methods from the CLI using batchMode, everything times out after 5 minutes of being idle. It doesn’t seem to matter what happens in the method, I have tried with a method that simply outputs a Debug.Log
and it still doesn’t work while Smart-Inspector is in the project.
I have tried both adding the plugin using a Git URL in Package Manager and by simply adding the directory to the project manually so I don’t think it’s related to the Package Manager.
Example command:
"C:\Program Files\Unity\Hub\Editor\2019.4.26f1\Editor\Unity.exe" -batchmode -projectPath / -nographics -executeMethod Custom.MyBuildScript.Build -silent-crashes -quit -logFile build.log
Output from batchMode:
Aborting batchmode due to failure:
Timeout while executing 'executeMethod' method 'Custom.MyBuildScript.Build'.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Command-line arguments
CLIBatchmodeCoroutines: How to use features that Unity supports when you launch the Unity Editor or a Standalone Player in batch mode.
Read more >Python Abort Running Script
This is the group repository for Smart Inspector project. Stop and pause applications. You have written some awesome R script, which does some...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, I can confirm that the
Application.isBatchMode
check fixed the issue. Thanks!Was it resolved?