Search Issue Tracker
Fixed
Fixed in 3.0.0-beta.5
Votes
8
Found in [Package]
3.0.0-beta.5
Issue ID
HUBX-663
Regression
Yes
[Hub][Linux] Sign in page redirects to blank browser page when signing in the Unity Hub
Reproduction steps:
1. Open the Unity Hub
2. Press Sign in
3. In the opened browser window enter your credentials
4. Press Sign in
Expected result: Unity Hub opens successfully
Actual result: Unity Hub doesn't open up, browser redirects to the blank page
Reproducible with: 3.0.0-beta.5
Not reproducible with: 2.4.5
Note:
- Sometimes after the 2nd step Unity Hub opens a blank browser page
- Workaround is to use Unity Hub 2.4.5
-
CodedOnes_Ai
Mar 22, 2023 09:08
For me, all I had to do was update my unity hub
-
nickretallack
Nov 22, 2022 06:20
Still broken in 3.3.0. Workarounds do not work. It does seem to trigger the app coming into the foreground after signing in, but it doesn't move on from there.
-
SeaWardDM
Oct 31, 2022 07:17
I'm having this happen right now in Unity Hub 3.3.0...wth?
-
sc-rumble
Mar 21, 2022 17:44
this is still broken on hub v3. The workaround I've found is that when you get the blank login page view the source and copy the unityhub link. Make sure unity hub is open and then run ./unityhub "unityhub://full-link-here" and you will get signed in. Trying to open the link without the hub open will not work.
-
hecker_de
Feb 06, 2022 00:37
I quite don't understand why the Hub should have to rely on some rather intransparent interaction for logging in, in the first place.
Even with the older version, some of the links in the "Learn" section (tutorials, but also downloading demo-projects had issues sometimes) never worked, they open a tab in my browser to `api.unity.com` for an OAuth2 interaction and all I get is an error message:
message: "Input Error"
code: "132.001"
details:
field: "token"
reason: "Query parameter is invalid. token does not exist" -
SalchipapasGames
Jan 20, 2022 13:48
Why is this shown as fixed? It's not!
-
bastianLstrube
Jan 17, 2022 11:50
This is NOT fixed in the unityhub 3.0.0 beta7.
blank page and unable to sign in.
-
kid510147
Dec 23, 2021 08:57
"
EVARINNOV 19, 2021 15:08
Hi,It seems to be caused because UnityHub is not registered to handle unityhub:// links
I've found a workaround that works with latest Hub:
- Lauch the UnityHub AppImage, click Sign In
- Enter the credentials
- In the blanck webpage you are redirected to, right-click -> show source. Copy the address starting with unityhub://
- close the UnityHub, open a terminal in the folder containing it, and start as a command :
./UnityHub.AppImage unityhub://<the-url-you-have-copied>And Unity Hub should start properly with you being logged in!
"This workaround can work to me. Thank you!
-
angusmf
Dec 13, 2021 15:08
This is NOT fixed
-
Evarin
Nov 19, 2021 15:08
Hi,
It seems to be caused because UnityHub is not registered to handle unityhub:// links
I've found a workaround that works with latest Hub:
- Lauch the UnityHub AppImage, click Sign In
- Enter the credentials
- In the blanck webpage you are redirected to, right-click -> show source. Copy the address starting with unityhub://
- close the UnityHub, open a terminal in the folder containing it, and start as a command :
./UnityHub.AppImage unityhub://<the-url-you-have-copied>And Unity Hub should start properly with you being logged in!
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note (fix version 3.0.0-beta.5):
Partially resolved if Linux users run the install scripts included with 3.0.0-beta.5. There is no automatic migration paths for users who receive an automatic update to beta 5.