Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X
Votes
21
Found in
2019.3.0a1
Issue ID
1397693
Regression
No
Building Unity player via CI results in "System.IO.IOException: Sharing violation on path" error
To reproduce:
• Currently no reproduction steps are known
Result: errors in CI: IOException: Sharing violation on path
Known platforms to reproduce the issue: Android, WebGL
Reproduced in (versions reported by the users): 2021.2.0f1, 2021.2.8f1
Not reproduced in (versions reported by the users) : 2021.1.x
Relevant Unity Forum posts:
https://forum.unity.com/threads/unable-to-build-player.1073420/#post-7628425
https://forum.unity.com/threads/build-failed-exception-occurred-inside-beedriver.1229508/
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
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
- Error "InvalidOperationException: You are trying to read Input using the UnityEngine.Input class, but you have switched active Input handling to Input System package in Player Settings." is present when using UI Toolkit and New Input System
- "Unable to get the list of approved APIs." is thrown when testing the App Packages with Windows App Certification Kit
- [Linux] The mouse wheel input is inverted when scrolling in the Build
razvan_stancu
Apr 07, 2023 14:27
Still reproduces on Unity 2021.3.18f1
aplusm
Feb 24, 2023 15:50
We're still running into this issue while building for Android on Jenkins with Unity 2021.3.19f1.
Can you please confirm the status of this issue?
ClockStoneAdmin
Aug 08, 2022 07:22
It turned out that logging to /dev/stdout caused the issue. As a workaround remove that command line parameter. See more info in the Unity forum thread "exception-occurred-inside-beedriver.1139905" (can't post direct link here unfortunately)
ClockStoneAdmin
Aug 08, 2022 07:20
It turned out that logging to /dev/stdout caused the issue. As a workaround remove that command line parameter. See more info here: https://forum.unity.com/threads/exception-occurred-inside-beedriver.1139905/
michael_house
May 20, 2022 02:18
Perhaps another datapoint, we only see this issue when building Test Player builds (i.e. Standalone test player builds for running Unity tests).
ClockStoneAdmin
Apr 15, 2022 06:32
We get this error when building on Mac via shell script invoked by Jenkins. Strangely the issue does not occur if I start the shell script manually. It seems to be somehow related to how the Jenkins client runs. It has the same user though (the same I am logged in when manually invoking the shell script)
Miguel_FirstLight
Apr 13, 2022 14:47
Happens also in 2021.2.17f1
tarrantulla
Mar 17, 2022 07:38
How to reproduce the issue on Unity 2021.2.0 - 2021.2.15 versions:
1. Create a new empty project
2. Add a build player Editor script so it can be run by CI
3. Add Google's External Dependency Manager (tested versions 1.2.167 and 1.2.168)
4. Some assets needs to be added. Based on the testing some assets have to be in the resources folder and some outside that folder accessing files, otherwise builds work as expected
a. An easy way to test is for example adding either SRDebugger https://assetstore.unity.com/packages/tools/gui/srdebugger-console-tools-on-device-27688 or Easy Roads https://assetstore.unity.com/packages/tools/modeling/easy-roads-mesh-gen-43327 asset
5. Try run either iOS build or Android build with IL2CPP backend triggered by a CI service
Expected result:
Build should be created successfully
What happens:
Error: Exception occurred inside BeeDriver: System.IO.IOException: Sharing violation on path
With an exact same project. if you run a build either in the editor or run it from terminal with a same build command as the CI system does (commanding it even from your own work machine to a remote build machine) the build works as expected.
With this error Unity 2021.2.x versions are basically unusable for us so this definitely needs fixing before going to LTS.