Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
v1.3.8
Issue ID
1261725
Regression
Yes
[Collab] "Operation is already running" error in Console during every Publish
To reproduce:
1. Open a Collab-enabled project.
2. Make a small change (ie, add a material, edit a published scene, etc.).
3. Open the Collaborate window.
4. Make sure All changes are selected and press the Publish button.
Expected: Changes are published with no errors in the Console.
Actual: Changes are published but in the Console the following error is displayed:
InvalidOperationException: {"code": 18, "detail": "Operation is already running"}
Unity.Cloud.Collaborate.Models.Providers.Collab.RequestPublish (System.String message, System.Collections.Generic.IReadOnlyList`1[T] changeEntries) (at Library/PackageCache/com.unity.collab-proxy@1.3.8/Editor/Models/Providers/Collab.cs:477)
...
Reproducible in 2020.2.0a16, 2020.2.0a18
Not reproducible in: 2020.1.0b17, 2020.2.0a15
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #1258770