Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2017.3.0p1
Issue ID
989074
Regression
Yes
[FixInGit1.5] Batch upload fails with Cannot Submit Change to Server from a relinked project
1. What happened
The issue comes from trying to upload a project that was unlinked and relinked within the same day. After creating a new project and enabling Collab I uploaded 15k assets successfully using 2017.2. I then unlinked, relinked the project in 2017.3 and attempted to upload my 15k assets (including .meta files) again. However, my upload fails after the first batch consistently with the following error message: "Cannot submit change to server." In some cases, this results in the first batch succeeding but the snapshot doesn't get updated to indicate that it succeeded. So there is a pending Update from the server that consists of the same files that were just uploaded. The best workaround is to avoid batch uploading and try partial publish to upload smaller selections of assets.
2. How we can reproduce it using the example you attached
a) Open the attached project with 15k assets in 2017.2.
b) Enable Collab.
c) Publish all assets using the Collab Toolbar.
d) Unlink the project, open it in 2017.3 and relink the project.
e) Enable Collab and Publish all assets again.
f) Wait for publish to fail (repeat if necessary).
g) Find the "Cannot Submit Change to Server" error in the Collab Toolbar and Editor log.
Reproduces on 2017.3.0f3 and 2018.1.0b3.
Does NOT reproduce in 2017.1.1f1 or 2017.2.0f3.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment