Search Unity

  1. Good news ✨ We have more Unite Now videos available for you to watch on-demand! Come check them out and ask our experts any questions!
    Dismiss Notice

Collaborate freeze unity with Check Workspace has not changed

Discussion in 'Unity Collaborate' started by lordubik, Apr 26, 2017.

  1. d1-favero

    d1-favero

    Joined:
    Oct 14, 2011
    Posts:
    9
    collab = time wasted waiting
     
    Marc-Saubion likes this.
  2. tcz8

    tcz8

    Joined:
    Aug 20, 2015
    Posts:
    373
    It'll be a week tomorrow, I sure hope it will be out. I wish you had a better turnaround time for issues like this. Its been a real issue for us.

    Also, if the "in progress" indicator inst allways reliable. Sometimes I end up working on the same scene as my collegue even tough I checked if it was "in progress".
     
    Last edited: Mar 20, 2018
  3. tcz8

    tcz8

    Joined:
    Aug 20, 2015
    Posts:
    373
    If what @Karsten mentioned is any indication, you may want to rethink that or you'll end up with an expansive bottle of vinegar :p

    But hopefully itll all be over soon.
     
  4. djweinbaum

    djweinbaum

    Joined:
    Nov 3, 2013
    Posts:
    525
    @ryanc-unity 2018.3.1p1 "check workspace has not changed" was able to finally finish this time (after about 20 min), but then the collab window went blank. The editor was still responsive, and I could see merge conflicts in my project view, and attempting to right click on the file in the project view and resolve by choosing one or diffing yielded no response. No editor log, no nothing. Restarting the editor didn't fix it. Reverting the whole project and trashing local changes did though, just like always. I had to ferry the updated files manually on a USB drive, as always.
     
    Marc-Saubion likes this.
  5. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Thank you for the update, @djweinbaum! I'm sorry that you encountered a blank collab window after the update. Our Support team would be happy to talk with you if you're still experiencing issues. Check out here for more info on how to get in touch with them.
     
  6. bradbecker

    bradbecker

    Joined:
    Dec 26, 2014
    Posts:
    103
    so did this get fixed in 2017.2 yet?
     
  7. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Not yet, but the fix will be in 2017.3.1p1. The backport for 2017.2 is still in progress.
     
  8. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
  9. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Hi @newlife! I'm sorry to say that the development cycle of 5.6 is coming to a close within the next month and no new updates (from Collab or anywhere else) will be making their way to it. Collab in 5.6 is such a different product in many areas compared to what it is now that backporting our biggest fixes would take too much time away from continuing to improve the overall experience. I know that this must be frustrating to users of 5.6 but we hope that in time you'll be able to give the latest versions of Unity a try and enjoy all the improvements that we've made so far (and that we will continue to make since 2017.4 will be our first Long Term Support version, which will receive critical updates up to two years after its release).
     
  10. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    This is a really bad news from you. Im sure that there are a lot of developers that are still using Unity 5.x. Btw, those bugs were known since more than one year. You should reconsider your decision.
    Most of long term, professional Unity users know very well that its really dangerous to upgrade to new unity version due to the "tendency" of adding new bugs at every release.
     
  11. Karsten

    Karsten

    Joined:
    Apr 8, 2012
    Posts:
    109
    I know its longer ago but since we enforce agressively Windows line endings only , with some tool (Strip,em) ,we dont see that problem anymore, so it looks like its as mentioned that the line endings play some role.
    Its just an idea but maybe you can make Unity doing this automatically depending on what platform it runs on.Since i know Unity the template script files are Apple line ending by default,i change mine after every Unity update to Windows line endings.
     
    Last edited: Apr 24, 2018
  12. akostrov

    akostrov

    Joined:
    Jan 26, 2016
    Posts:
    4
    It's very permanent problem, version Unity 2017.3.1f1, when the issue will be resolved?
     
  13. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
  14. akostrov

    akostrov

    Joined:
    Jan 26, 2016
    Posts:
    4
  15. Jerkins

    Jerkins

    Joined:
    Jul 15, 2016
    Posts:
    1
    I think trouble with scene merge system. delete your updated sceneㅋㅋ ㅆㅂ
     
  16. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Hi @Jerkins, I'm sorry to hear that you're having scene merge issues. Can you give some more details about what's happening? Are all of your local changes being deleted after you update your scene? Are you making sure to save your changes before you Update?
     
  17. Hopper_Fassker

    Hopper_Fassker

    Joined:
    Oct 14, 2019
    Posts:
    1
    I use this version. -> Unity 2019.2.8f1
    The version has this issue.
    How can use Unity Collabo without this issue?
     
  18. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Hi @Hopper_Fassker, could you please elaborate? Are you experiencing a freeze with the "Checking Workspace for Changes" message? Can you go into your Package Manager and tell me if you're using v1.2.16 or v2.0 of Unity Collaborate? If you're using v1.2, could you try v2.0 and see if you still experience the issue?
     
  19. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    Hello I still keep losing connection with collab with this error:
    ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.
    This happen A LOT of time every day and causes collab to reconnect to the server and request for changes several times per day (a least three times).
    How can this is possible for a paid service? Its getting worst and worst, I just read the Unity has increased the price for the subscriptions. Im really getting mad. You make your services worst and you increase the price.
    Im using Unity 2018.4.10 LTS and collab 1.2.15.
     
  20. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Hi @newlife, this error pops up when the authentication service for Unity does not respond to Collaborate's checks. This can happen after leaving the project open overnight and then coming back to it after waking up your machine. If the error pops up more often than that then it is very likely that something is interfering with your connection to Unity's authentication service. Are you running through a VPN or firewall where you are? Can you try disabling them if you are and see if you still encounter this error?
     
  21. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    As I wrote, those errors happen A LOT of times every day, not night,while Im working on the project.
    I dont have any VPN or firewall, apart the windows standard firewall. More, nothing has changed in my configuration (PC, connection, firewall, etc) since it was working (several months ago).
     
  22. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    That is really frustrating and I'm sorry you're seeing those errors so often. You mentioned that you were using 1.2.15 of the Collab package. Could you try upgrading to 1.2.16 and see if that helps reduce the frequency of the errors? Could you also try 2.0-preview.17 of the Collab package if you're still seeing this error?
     
  23. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    Still facing those errors. Its clearly an issue of collab server. Don't ask me to try a preview package on a important production project.
     
  24. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    These are the errors related to collab that I found in the editor log:


    Built from '2018.4/staging' branch; Version is '2018.4.11f1 (7098af2f11ea) revision 7379119'; Using compiler version '191326128'
    OS: 'Windows 8.1 (6.3.0) 64bit' Language: 'en' Physical Memory: 14270 MB
    BatchMode: 0, IsHumanControllingUs: 1, StartBugReporterOnCrash: 1, Is64bit: 1, IsPro: 1
    [Package Manager] Server::Start -- Port 49811 was selected
    ListPackages failed, output: {
    "name": "unity-editor",
    "version": "5.7.0",
    "problems": [
    "extraneous: unityeditor-collab-history@0.6.10 C:\\Users\\michele\\AppData\\Roaming\\Unity\\Packages\\node_modules\\unityeditor-collab-history"
    ],
    "dependencies": {
    "unityeditor-collab-history": {
    "version": "0.6.10",
    "extraneous": true,
    "problems": [
    "extraneous: unityeditor-collab-history@0.6.10 C:\\Users\\michele\\AppData\\Roaming\\Unity\\Packages\\node_modules\\unityeditor-collab-history"
    ],
    "from": "unityeditor-collab-history.0.6.10.tgz",
    "resolved": "file:unityeditor-collab-history.0.6.10.tgz"
    },
    "unity-editor-home": {
    "version": "2.2.1",
    "from": "unity-editor-home.2.2.1.tgz",
    "resolved": "file:unity-editor-home.2.2.1.tgz"
    },
    "unityeditor-cloud-hub": {
    "version": "0.0.15",
    "from": "unityeditor-cloud-hub-0.0.15.tgz",
    "resolved": "file:unityeditor-cloud-hub-0.0.15.tgz"
    },
    "unityeditor-collab-toolbar": {
    "version": "0.7.16",
    "from": "unityeditor-collab-toolbar.0.7.16.tgz",
    "resolved": "file:unityeditor-collab-toolbar.0.7.16.tgz"
    }
    }
    }


    Failed to free the context in 1000 milli seconds
    [Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 65)

    [Collab 2019-1026 21:15:59 GMT][Error] 'Cannot get revision from server' (8) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/RevisionRequests.cpp' at line 187
    [Collab 2019-1026 21:15:59 GMT] GetLatestRevisionRequest failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/projects/a30936b8-9a2a-42a6-bebf-5a646621aa46/branches/master/revisions?limit=1 Result: {"server":"collab-64c758f56b-blvbv","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-10-26T21:15:59.650Z","request_id":"e55541df-7770-4a59-8ef0-9d3ed1d8f29a","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"49fb3729-1f07-4c50-a66c-20eef9afca7d"}
    [Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 65)

    [Collab 2019-1026 21:15:59 GMT][Error] 'Unable to refresh channel access' (51) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 250
    [Collab 2019-1026 21:15:59 GMT] RefreshChannelAccessRequestInternal failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/refresh_channel_access/ Result: {"server":"collab-64c758f56b-qhn4p","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-10-26T21:15:59.846Z","request_id":"996c5b0a-63c3-4681-8259-e6758ce1ebae","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"6db89765-cd54-4581-b796-e4425c454ab2"}
    [Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 65)

    [Collab 2019-1026 21:16:00 GMT][Error] 'Unable to refresh channel access' (51) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 250
    [Collab 2019-1026 21:16:00 GMT] RefreshChannelAccessRequestInternal failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/refresh_channel_access/ Result: {"server":"collab-64c758f56b-qhn4p","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-10-26T21:16:00.631Z","request_id":"51f9a0ed-e794-42bf-aa3b-01631aa947a3","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"4752a7f0-ccce-4564-a341-63d18883a5e0"}
    Project ID request failed, Reason: The requested URL returned error: 401 Unauthorized (401).
    Unknown Unity Connect error (400). Please contact support at support@unity.com while processing request "https://core.cloud.unity3d.com/api/projects/a30936b8-9a2a-42a6-bebf-5a646621aa46", HTTP error code 401
    .[Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 65)

    [Collab 2019-1026 21:16:00 GMT][Error] 'Unable to get soft locks' (54) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 112
    [Collab 2019-1026 21:16:00 GMT] GetAllSoftLocksRequestInternal failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/projects/a30936b8-9a2a-42a6-bebf-5a646621aa46/branches/master/locks?machine_id=PGKr9iUAA7APC9Ii3yNaURHIzwQ%3D&local_path=C%3A%2FUnity%20Projects%2Fgentl%2FGentlemen_Racing Result: {"server":"collab-64c758f56b-xcdkb","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-10-26T21:16:00.997Z","request_id":"5e9fa1dc-232a-4498-b8f9-d5585c04f517","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"b072f156-6562-4ca1-bded-df54dc8b2cd2"}
    [Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 65)

    [Collab 2019-1026 21:16:00 GMT][Error] 'Unable to refresh channel access' (51) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 250
    [Collab 2019-1026 21:16:00 GMT] RefreshChannelAccessRequestInternal failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/refresh_channel_access/ Result: {"server":"collab-64c758f56b-xcdkb","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-10-26T21:16:01.257Z","request_id":"26b1077c-de7f-4446-aa0c-1d332ea320b3","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"0d20b3c9-816c-49d0-a058-c999f9dda62f"}
    Project ID request failed, Reason: The requested URL returned error: 401 Unauthorized (401).
    Unknown Unity Connect error (400). Please contact support at support@unity.com while processing request "https://core.cloud.unity3d.com/api/projects/a30936b8-9a2a-42a6-bebf-5a646621aa46", HTTP error code 401
    .
     
  25. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    Any news? these kind of errors are not acceptable and should have highest priority, we are talking about a paid service.
     
  26. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Hi @newlife, thank you for your patience. Regarding upgrading your package, you don't need to try the preview build if you're not comfortable using it for your production project. However, our v2.0 preview package's main focus was to remove the "Checking for changes" dialog so that it doesn't block any actions. I'd strongly recommend trying it to see if it resolves your issues.

    We also looked at your logs on our backend each time you've encountered the ExternalAPI:Failure issue and, from what we can see, it looks like the issues with connecting to our authentication service resolved themselves within a second of them happening, so you should be safe to ignore those errors. If this error triggers a check for changes each time then this would be resolved by upgrading to our preview build.

    Please let me know if you're able to give v2.0 of our package a try and if you encounter any issues with that.
     
  27. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    So you are telling me that you are not going to fix a serious issue of a paid service asking me to update to a PREVIEW package? Can you please tell what "preview package" stands for?
    I think that stands for: DO NOT USE FOR PRODUCTION PROJECTS.
    Please fix this issue, this is a paid service.
     
  28. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    I completely understand not wanting to use a preview build for your production project. In https://forum.unity.com/threads/cho...es-1-2-16-and-2-0-preview-15-packages.683197/, we discussed the differences between using v1.2 and v2.0 of Collaborate. In short, while v2.0 address the "Checking for Changes" dialog issue, it also offers such a different workflow compared to v1.2 that we wanted to keep both versions and allow users to choose the version that worked best for their needs (automatic detection of changes was no longer possible in most cases with v2.0 like it was in v1.2).

    We would love to have been able to back port the "Checking for Changes" fix in v2.0 to v1.2. However, this change required a massive refactor of the backend architecture to allow this to work as users expected, which made it impossible to back port to earlier versions. We ultimately plan to combine the efforts in both versions of Collaborate into one but we've had to shift focus from that to implement the new UX. Otherwise, without this new UX, which will no longer use an outdated framework that is being deprecated in 2020.1, the Collaborate Toolbar won't exist.

    We really appreciate your patience with us while we work to resolve these issues while under such tight deadlines.
     
  29. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    From your answer is not clear, so im going to ask you clearly:
    Are you going to fix this "HTTP status 401 Unauthorized" error in collab .1.2.16?
     
  30. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Sorry for the confusion, I assumed you were referring to being primarily annoyed by the "Checking for changes" dialog since you were posting in the thread about that issue.

    We are tracking this bug and will work on a fix for it after we get the new UX package out.
     
  31. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    Anyway, I tested collab 2.0 on a minor project, and it seems that "HTTP status 401 Unauthorized" error is snot occurring (was occurring with collab 1.2.16).
     
  32. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    I was wrong, the issue is present also with collab 2.0 preview 17 (and Unity 2019.1.7).
    This is clearly an issue SERVER SIDE. Please fix this ASAP.


    CollabProxyException: failed to parse supported auth schemes: The operation identifier is not valid.

    UnityEngine.Debug:LogError(Object)
    CollabProxy.Client.CollabVersionControl:LogExceptionDetails(Exception) (at Library/PackageCache/com.unity.collab-proxy@2.0.0-preview.17/Editor/Client/CollabVersionControl.cs:445)
    CollabProxy.Client.CollabVersionControl:OnUpdateHeadException(Exception) (at Library/PackageCache/com.unity.collab-proxy@2.0.0-preview.17/Editor/Client/CollabVersionControl.cs:224)
    CollabProxy.Client.<>c__DisplayClass18_0`1:<RegisterListener>b__0(PacketHeader, Connection, String) (at Library/PackageCache/com.unity.collab-proxy@2.0.0-preview.17/Editor/Client/CollabProxyClient.cs:286)
    NetworkCommsDotNet.Tools.PacketTypeHandlerDelegateWrapper`1:Process(PacketHeader, Connection, Object)
    NetworkCommsDotNet.Connections.Connection:TriggerSpecificPacketHandlers(PacketHeader, Object)
    NetworkCommsDotNet.NetworkComms:TriggerAllPacketHandlers(PacketHeader, Connection, MemoryStream, SendReceiveOptions, Boolean)
    NetworkCommsDotNet.NetworkComms:TriggerAllPacketHandlers(PacketHeader, Connection, MemoryStream, SendReceiveOptions)
    NetworkCommsDotNet.NetworkComms:CompleteIncomingItemTask(Object)
    NetworkCommsDotNet.Tools.CommsThreadPool:ThreadWorker(Object)
    System.Threading.ThreadHelper:ThreadStart(Object)



    [Collab 2019-1103 10:53:20 GMT][Error] 'Cannot get revision from server' (8) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/RevisionRequests.cpp' at line 186
    [Collab 2019-1103 10:53:20 GMT] GetLatestRevisionRequest failed, Reason: 0 Url: https://collab.cloud.unity3d.com/api/projects/5590a145-e4d0-4561-b3aa-b062a10c91ad/branches/master/revisions?limit=1 Result:
    [Collab 2019-1103 10:53:20 GMT][Error] 'Unable to refresh channel access' (51) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 249
    [Collab 2019-1103 10:53:20 GMT] RefreshChannelAccessRequestInternal failed, Reason: 0 Url: https://collab.cloud.unity3d.com/api/refresh_channel_access/ Result:
    CollabProxyException: failed to parse supported auth schemes: The operation identifier is not valid.

    UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
    UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
    UnityEngine.Logger:Log(LogType, Object)
    UnityEngine.Debug:LogError(Object)
    CollabProxy.Client.CollabVersionControl:LogExceptionDetails(Exception) (at Library\PackageCache\com.unity.collab-proxy@2.0.0-preview.17\Editor\Client\CollabVersionControl.cs:445)
    CollabProxy.Client.CollabVersionControl:OnUpdateHeadException(Exception) (at Library\PackageCache\com.unity.collab-proxy@2.0.0-preview.17\Editor\Client\CollabVersionControl.cs:224)
    CollabProxy.Client.<>c__DisplayClass18_0`1:<RegisterListener>b__0(PacketHeader, Connection, String) (at Library\PackageCache\com.unity.collab-proxy@2.0.0-preview.17\Editor\Client\CollabProxyClient.cs:286)
    NetworkCommsDotNet.Tools.PacketTypeHandlerDelegateWrapper`1:Process(PacketHeader, Connection, Object)
    NetworkCommsDotNet.Connections.Connection:TriggerSpecificPacketHandlers(PacketHeader, Object)
    NetworkCommsDotNet.NetworkComms:TriggerAllPacketHandlers(PacketHeader, Connection, MemoryStream, SendReceiveOptions, Boolean)
    NetworkCommsDotNet.NetworkComms:TriggerAllPacketHandlers(PacketHeader, Connection, MemoryStream, SendReceiveOptions)
    NetworkCommsDotNet.NetworkComms:CompleteIncomingItemTask(Object)
    NetworkCommsDotNet.Tools.CommsThreadPool:ThreadWorker(Object)
    System.Threading.ThreadHelper:ThreadStart_Context(Object)
    System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean)
    System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean)
    System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object)
    System.Threading.ThreadHelper:ThreadStart(Object)

    (Filename: Library/PackageCache/com.unity.collab-proxy@2.0.0-preview.17/Editor/Client/CollabVersionControl.cs Line: 445)

    at LibGit2Sharp.Core.Ensure.HandleError (System.Int32 result) [0x00059] in <5e2d125af12e4bcc982f89d05fe51418>:0
    at LibGit2Sharp.Core.Ensure.ZeroResult (System.Int32 result) [0x00004] in <5e2d125af12e4bcc982f89d05fe51418>:0
    at LibGit2Sharp.Core.Proxy.git_remote_fetch (LibGit2Sharp.Core.Handles.RemoteHandle remote, System.Collections.Generic.IEnumerable`1[T] refSpecs, LibGit2Sharp.Core.GitFetchOptions fetchOptions, System.String logMessage) [0x00028] in <5e2d125af12e4bcc982f89d05fe51418>:0
    at LibGit2Sharp.Commands.Fetch (LibGit2Sharp.Repository repository, System.String remote, System.Collections.Generic.IEnumerable`1[T] refspecs, LibGit2Sharp.FetchOptions options, System.String logMessage) [0x000e5] in <5e2d125af12e4bcc982f89d05fe51418>:0
    at CollabProxy.GitProxy.FetchRemoteChanges (System.String accessToken) [0x0008d] in <ccb4add59c334adf88717235d10ab5c2>:0
    at CollabProxy.GitProxy.SetCurrentHeadAsync (System.String revisionId, System.String accessToken) [0x0002c] in <ccb4add59c334adf88717235d10ab5c2>:0
    [Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 61)

    [Collab 2019-1103 10:53:21 GMT][Error] 'Unable to refresh channel access' (51) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 249
    [Collab 2019-1103 10:53:21 GMT] RefreshChannelAccessRequestInternal failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/refresh_channel_access/ Result: {"server":"collab-7998cb7c68-7nwqp","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-11-03T10:53:21.462Z","request_id":"aa5e9054-eb3b-43d4-9c9e-3196d73ba8b5","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"740612d4-7a37-44b8-9190-7a8ee7fdb144"}
    [Collab] ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.

    (Filename: C:\buildslave\unity\build\Editor/Src/Collab/CollabCommon.cpp Line: 61)

    [Collab 2019-1103 10:53:22 GMT][Error] 'Unable to refresh channel access' (51) returned in 'C:\buildslave\unity\build\Editor/Src/Collab/Requests/SoftLocksRequests.cpp' at line 249
    [Collab 2019-1103 10:53:22 GMT] RefreshChannelAccessRequestInternal failed, Reason: 401 Url: https://collab.cloud.unity3d.com/api/refresh_channel_access/ Result: {"server":"collab-7998cb7c68-qqzj7","detail":"ExternalAPI::Failure: A request to Unity accounts has failed with HTTP status 401 Unauthorized. Please try again. If you continue to see this error, please restart Unity.","date":"2019-11-03T10:53:22.463Z","request_id":"1d2093ee-43b7-4d6b-b781-6b8a5bd82909","code":"INTERNAL","original_uri":"http://localhost:5001/v1/core/api/users/me","orginal_status":401,"original_body":{"message":"Expired Access Token","code":"132.108","details":[{"field":"access_token","reason":"The access_token is already expired"}]},"orginal_request_id":"f1924ca1-595d-4933-9849-4ce104a58d62"}
    Project ID request failed, Reason: Receiving data failed with unitytls error code 7 (401).
    Unknown Unity Connect error (400). Please contact support at support@unity.com while processing request "https://core.cloud.unity3d.com/api/projects/5590a145-e4d0-4561-b3aa-b062a10c91ad", HTTP error code 401
     
  33. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    when this UX package will be out?
     
  34. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    We're aiming to release the new UX with 2020.1.
     
  35. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    This is not acceptable. It means that you are going to fix this important bug AFTER the release of unity 2020.1.
    I remind you that 2019.1 has been released in Apr 16th, 2019.
    This can mean that you are going to fix this issue AFTER April 2020, more than FIVE months from now.
    Please reconsider this, I showed you that this issue is present in collab 2.0 too, not only in 1.x.
     
  36. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    We actually released an initial version of the new UX in v1.2.17, which you can try out with 2020.1.0a13 or newer. You can learn more about the package update in our post about its release. While 2020.1 is planned to release around April, our team will still be able to work on important bugs for older versions in the meantime, so we will plan to have a fix out before then.

    Please keep in mind that development across Unity will slow down significantly during the winter break, but will ramp back up soon after. We will update everyone on the progress of our bug fixes when we have more information.
     
  37. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    This is too vague. Please be more precise.
     
  38. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    That's enough. Things are getting worse and worse. Its not possible to accept this anymore.
    Now every couple of hours collab gives this stupid "HTTP status 401 Unauthorized" error and this causes EVERY TIME a request for changes from the server. This error occurs both in collab 1.2 and collab 2.0, so this is clearly a SERVER SIDE error.
    We are paying a service sold as "ready and stable" and this is not working even just for a cloud backup.
    PLEASE stop working on LOW priority stuff like "new UX" and fix this urgent bug. A lot of people around the world is facing it.
    Otherwise, I'll call everyone who think that this is not acceptable to join in a class action.
     
    Marc-Saubion likes this.
  39. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    I'm sorry that you feel that way, but this new UX is not a low priority for Collaborate. We need to update to a new, more stable backend because the old one is being deprecated in 2020.1. Without this new UX, Collaborate will not exist in any version newer than 2020.1. The 401 Unauthorized error is a client side issue with how the Editor is calling our services so we cannot just fix it immediately on the server side. We understand the pain this is creating for you and some users and we want to fix it as soon as possible. We're sorry for the delay and appreciate your understanding.
     
  40. AcidArrow

    AcidArrow

    Joined:
    May 20, 2010
    Posts:
    7,139
    So, will 1.3.2 eventually be backported to 2019/2018?
     
  41. SValdenegroKlu

    SValdenegroKlu

    Joined:
    Oct 8, 2019
    Posts:
    2
    Collab sucks, for real. I've wasted a whole day redownloading the whole project because of workspace changes. How's Unity going compensate for a whole day of work lost?
     
    Marc-Saubion likes this.
  42. ryanc-unity

    ryanc-unity

    Unity Technologies

    Joined:
    Mar 23, 2016
    Posts:
    1,723
    Hi @AcidArrow, unfortunately, we won't be able to back port 1.3.2 to 2019 or older because the new UI is built on UIElements, which was experimental and not feature-complete in 2019 and not available in 2018. While the new UI cannot be back ported, we will continue to back port high priority bug fixes to 2019 and 2018 LTS for as long as they're supported.

    Hi @SValdenegroKlu, I'm sorry that you're having difficulties with Collab. If you run into the "Check workspace has not changed" error again then could you try closing Unity, deleting your CollabSnapshot file in the Library/Collab folder, then reopening your Project to see if it works again? If that doesn't work then we recommend re-downloading your Project from the Cloud.
     
  43. Marc-Saubion

    Marc-Saubion

    Joined:
    Jul 6, 2011
    Posts:
    405
    I'd gladly give my support.

    I'm baffled that this check for changes and UI issues are still a thing considering a fix was already months late and about to be released a year ago when I stopped using Collaborate.

    Since this service is part of my subscription despite the fact that it's not production ready and not a priority according to @ryanc-unity , Unity shouldn't be allowed to charge us for it.
     
  44. newlife

    newlife

    Joined:
    Jan 20, 2010
    Posts:
    882
    Im sorry but we dont understand (and accept) this. Do you realize that BOTH 1.2.x AND 2.0 VERSION OF COLLAB SUFFERS OF THIS ISSUE? HOW CAN YOU SELL A SERVICE THAT IS NOT WORKING? THERE IS NO COLLAB VERSION RIGHT NOW THAT IS NOT AFFECTED BY THIS SERIOUS ISSUE AND YOU ARE STILL SELLING IT AS PERFECTLY WORKING AND RELIABLE.
    IF THIS IS A CLIENT SIDE ISSUE WHY YOU DONT FIX IT? HOW CAN YOU THINK THAT THIS IS NOT HIGHER PRIORITY RESPECT OF NEW UX?

    Do you understand that this is perceived by us as a complete thoughtlessness of unity towards us paying user?
    If you still have a grain of respect of people who pay your salary, please tell WHEN THIS ISSUE WILL BE FIXED FOR 2018 / 2019.
     
    Marc-Saubion likes this.
  45. Alterego-Games

    Alterego-Games

    Joined:
    Jul 13, 2015
    Posts:
    40
    While I understand that the comment from newlife is a bit aggressive do I feel the anger too.

    We've been paying for Collab for over a year now, and while it was buggy in the 2017 version, its absolutely unusable in 2018/2019 for the projects we are currently working on. 1.2.x freezes our projects for over 5 minutes every time you pull something, looses connection often (so checking for changes dialogue starts again) or requires a "re-pull". meaning a 15 to 30 minute hang for each of our developers at the end of the day.

    version 2.0 has some concept improvements but is SO buggy that it is unusable in its own way.

    So hearing that the projects in 2018 and 2019 will NEVER get a working collaborate version makes me very, very angry that we are paying for a "stable and release worthy" piece of software that in fact is super broken.

    I very much hope, that we can get the priority back to 2018 LTS and 2019 LTS version to get proper Collab support instead of 2020 alpha/beta support. Since I think a lot of us that use Unity in a professional capacity couldn't care less about 2020, because ALL our projects are build on LTS versions.

    Please, please give us a workable sollution. I've been wasting two days on Collab now this week.
     
    Marc-Saubion likes this.
  46. Alterego-Games

    Alterego-Games

    Joined:
    Jul 13, 2015
    Posts:
    40
    And if you can't fix it, could you let us go back to the Collab version of 2017? At least in that collab version, the only bug we often had were missing files in a pull. We then just had to reboot Unity (no Checking for Changes!!!) and we were good to go.
     
  47. Marc-Saubion

    Marc-Saubion

    Joined:
    Jul 6, 2011
    Posts:
    405
    Delete Collab from your project and try Plastic SCM. First month was free last year when I tried it and I never went back. It can't hurt to give it a shot.
     
unityunity