Hello,
When I click sign in on UnityHub, it takes me to this white login screen, which does nothing. And thus I decided to click the link,and that also does nothing. I’m stuck in a loop of clicking sign in, and being taken to this white page.
I’ve tried reinstalling Unity, rebooting laptop,clearing browser cookies,changing browser but to no avail.
(I run UnityHub 3.8.0).
Any help would be appreciated.
I’m having a similar problem, both on Mac and Windows. But for me rebooting seems to fix things.
The first time I start Unity Hub after a reboot I am automatically logged in, and I get my normal list of projects. But if I ever quit Unity Hub I get that screen that is shown by the OP, and pressing “sign in” does nothing. I’ve tried force-quitting all Unity Hub and License manager and related processes, to no avail. But reboot seems to cure it.
Same here. I’m getting following errors when it opens the sign in view when looking at the Chrome dev tools in Unity Hub:
Error: Error invoking remote method ‘common/rendererInitialized’: No handler registered for ‘common/rendererInitialized’
Error: Error invoking remote method ‘apm/notifyFirstPageLoad’: No handler registered for ‘apm/notifyFirstPageLoad’
Error: Error invoking remote method ‘redirect/openSignIn’: No handler registered for ‘redirect/openSignIn’
{
“name”: “Error”,
“message”: “Error invoking remote method ‘externalService/getExternalUrl’: No handler registered for ‘externalService/getExternalUrl’”,
“stack”: “Error: Error invoking remote method ‘externalService/getExternalUrl’: No handler registered for ‘externalService/getExternalUrl’”
}
I am also having the same error, I’m on Mac Sonoma, 14.3.1:
WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
Error occurred in handler for 'localConfig/getHubConfig': No handler registered for 'localConfig/getHubConfig'
Error occurred in handler for 'featureFlags/getFeatureFlags': No handler registered for 'featureFlags/getFeatureFlags'
Error occurred in handler for 'auth/getUserInfo': No handler registered for 'auth/getUserInfo'
Hello, I was able to fix this issue by running the executable. If that fails, delete all unity files from your device, re install it and try again.
i cant still log in no matter what im doing it dosent let me open unity hub!..same issue!
Same issue here since the most recent hub update. Similar problem also occurred on my mac but re-installing hub worked there (it just made it worse on my main pc though).
edit:
I found it to be a network issue that is probably local. Some other secure apps/programs (ones with login/protective features) weren’t connecting to the internet successfully however my browser and less secure programs were working normally. Resetting my ethernet adapter, PC and my modem fixed the issue for me. However, this could be a red herring from my experience and could have just brought the same issue to light as I have had the issue occur on two devices since hub 3.9.0.
Same issue fedora 40
I have the same problem, but on Linux Ubuntu
I am having the same problem now since updating Unity Hub to 3.10
I’m on Windows 10 and using Firefox.
*I tried setting my default browser to Edge, that made it work.
when you log in into the hub it actually opens a browser page and you login on that page.
why it does this and can’t just login by itself? must be some “honey” like shenaning that I don’t have the knowledge to verify. how unity hub gets informed that firefox has logged into a unity account? why firefox lets a different app like unityhub check info on a page inside the browser?
try setting the default browser to edge maybe that one works? it opens a firefox page at least?
@altepTest in this case there is a very legitimate reason for this going via the browser. It is an authentication protocol called OAuth2 (you can look it up). The whole point is that the app (in this case Unity Hub) does not have to know your password but can still be sure that you are you. And if you were using a non-password authentication device the app doesn’t have to learn about this. OAuth2 and the browser take care of everything.
It appears unityhub installs a mime-handler file in /usr/share/applications/unityhub.desktop but it doesn’t get registered so it doesn’t do anything.
To fix this on debian:bookworm, you can follow steps similar to https://askubuntu.com/a/1023143
I ran these commands:
sudo apt-get install desktop-file-utils
sudo update-desktop-database
xdg-mime default unityhub.desktop x-scheme-handler/unityhub
Perhaps they (or something similar) need to be added to the unityhub install scripts for Ubuntu/Debian.
I also made sure there was an entry network.protocol-handler.expose.unityhub = true in Firefox, although this didn’t seem to have any effect on its own.
Thanks bro I reboot my system and it worked without even showing me the login screen
Hello everyone,
Not sure if this will help, but after exiting, checking connection and many of the other suggestions I found after 2 hours of searching, what finally worked for me was going into Appdata/Roaming and deleting the Cache folder. Sign in worked automatically upon my next launch of the program. Hope this helps!!!
I also encountered this issue. I found that this occurs due to install new browser I installed. After uninstall it, it automatically singed in to the Unity Hub. So please check your default browser settings and check if it has been changed.
I needed a couple more steps to fix /usr/bin/xdg-mime: 856: qtpaths: not found at step 3:
sudo apt-get install qt6-base-dev-tools
sudo ln -sf /usr/bin/qtpaths6 /usr/bin/qtpaths