Collaborate null error

When using collaborate (1.5.7 version, newest), following error occurs,

NullReferenceException: Object reference not set to an instance of an object
Unity.Cloud.Collaborate.UserInterface.CollaborateWindow.OnDisable () (at Library/PackageCache/com.unity.collab-proxy@1.5.7/Editor/Collaborate/UserInterface/CollaborateWindow.cs:86)


How to resolve this?

 

I am getting the same error as of yesterday. Also using 1.5.7

 

Same here.
NullReferenceException: Object reference not set to an instance of an object
Unity.Cloud.Collaborate.UserInterface.CollaborateWindow.OnDisable () (at Library/PackageCache/com.unity.collab-proxy@1.5.7/Editor/Collaborate/UserInterface/CollaborateWindow.cs:86)

 

Smells like Collaborate has a bug. See if you can figure out where it stores its preferences and delete them. Or perhaps try a slightly-earlier version, see if that works.

You may wish to invest in the brainspace to use an industry-grade source control system. If you go for a job where such a system is in use, having the experience will be helpful.

Personally I use git because it is free and there are tons of tutorials out there to help you set it up.

Here's how I use git in one of my games, Jetpack Kurt:

https://forum.unity.com/threads/2-steps-backwards.965048/#post-6282497

Using fine-grained source control as you work to refine your engineering:

https://forum.unity.com/threads/whe...grammer-example-in-text.1048739/#post-6783740

Share/Sharing source code between projects:

https://forum.unity.com/threads/your-techniques-to-share-code-between-projects.575959/#post-3835837

Setting up the right .gitignore file:

https://forum.unity.com/threads/removing-il2cpp_cache-from-project.1084607/#post-6997067

 

@Kurt-Dekker
But Git doesn't support asset and scene merging? and free Git only gives 300 MB total space?

Then so only use Git as Script merging?

and Assets(models, images,,) and Scene file manually copying by USB offline?

 

It's a text file, any version control can merge it more or less successfully.
If you use Git, you should use LFS too (for the binary files).
- GitHub supports 500 megabytes projects.
- Bitbucket gives you 1Gb LFS
- Azure Repos (Azure Devops feature) gives you unlimited repos, repo sizes, unlimited LFS storage for persons and small teams (also can be used with Git or with Team Foundation)

Spoiler: This is a scene file source

It's an image, because the forum software ate the text source for some reason.

 

There are many git servers with many free plans which have many different capabilities. Gitlab's free repos can be up to 10GB.

 

Git itself supports repositories of unlimited size essentially.

As others point out, LFS can help you manage larger files.

You can always push or pull a repo of any size to a thumb drive, which works great for backups.

 

Just upgraded to 1.5.7 and got this Null exception. Normally I use collab only for some quick testing .. Probably don't update to this version yet.

 

Same here. I started to get this error after updating to 1.5.7

 

Got this error after updating as well. Reverting back to 1.3.9 using the package manager (look under "Version Control") fixed the issue.

 

I just went from 1.5.7 to 1.3.9 and it just added yet another error for me :/

 

Has there been any updates for the error:
Unity.Cloud.Collaborate.UserInterface.CollaborateWindow.OnDisable

 

I just updated to 2021.9 and with it updated to Version Control 1.57 and received this error. I just went to package manager, clicked "remove" version control. Then went back to Package Manager under Unity Registry and found and installed Version Control again. Error gone.

 

That did not work for me @Sparty93

 

Does this error cause your editor to freeze? lately 2020.3 is freezing all the time here and when I check the logs the only thing I see with an error is this...
I dont know what else could be causing it.
I'm using 2020.3.11

 

I've had this bug since the upgrade to 2021.1.9 - checked my VC after reading other posts - I'm also on VC 1.57. Reinstalling the component doesn't work for me, either.

Occurs every time I compile or enter play mode. Not crashing the editor yet, but noticeably slowing compile / serialization. UGH!

 

I just remove the version control package and the error is gone

 

Yeah. This bug caused me to stop using/paying for collaborate.
Unity only seems to respond to issues that they plan to fix.

 

yea But some people might be using that collaborate for version control so we can do like that

 

Related issue : https://issuetracker.unity3d.com/is...exception-errors-when-hidden-on-domain-reload

 

i use version control in collaborate, any updates on the error?

 

I believe that if you close the collab window in the Inspector the error will be gone, still testing tho

 

Same error here- Please fix.

 

same problem for me, it doesn't affect my project but is very annoying...

 

Hi Close Collaborate Window and reopen it (Window ->Collaborate) this helps me

 

Same here. I upgraded the pkg to preview 2.x version then the error gone.

 

Like @AquariuZ said, a workaround for this is to simply close the Collaborate tab and keep it closed up until you need to use it again. Sync, then close again.

 

This has worked for me.

 

Close the tab and turn it back on would solve this.

 

Same here. Closing the Collaborate window/tab and reopening it removed the error for me.

 

I had the same issue, using 2020.3.12. Somehow the error doesn't appear when i have the collaborate tab onscreen. Really don't know why this is happening but it works for me

 

thank you jesus. this worked for some dumb reason

 

Thaaanks

 

does not work for me! Unity, fix this ASAP!

 

remove version contron. Update to 1.7.1 from Collaborate Window. Error will be gone

 

This seems to work, thank you very much!

 

Removing version control works for me

 

I have updated Unity Collaborate to the latest version. And then I can fix it.

 

I can't update to anything newer than 1.5.7 in 2020.3.13f1 without getting compilation errors.

However, it seems like the process of updating to 1.8.0 (and then reverting back down to the verified 1.5.7 release) resolved this. So, that's still worth a shot if you're running into this!

(ah, nevermind, it's back again)

 

I also had to remove version control to update to 1.8.0

 

Removing the "version control" from ((PackageManager/PackagesInProject/VersionControl)) helped. Appreciate it!