The Hub was removing old sub-versions which is not ideal since installing those manually I cannot easily select or add components later. But now also the beta disappeared.
To install, I must go to the site and click the install from hub button
And no option to select rc either
My hub offered 2019.3 as a download for a released version…
Yep I have the same issue right now. Could download the RC at home last night, but currently no 2019.3 (beta or RC) on Hub atm. But yes the “download with Hub” link on web works.
I think 2019 release is near. It appeared as f1 in my hub then disappeared again.
I must have gotten in when it was on and then taken off again
We’re aware of the issue and it will be fixed in the 2.2.1 release of the Hub. You can get 2019.3.0f1 here in the meantime: Unity 2019.3.0f1
5 Likes
Any timeframe for Hub 2.3?
you can also trick hub into grabbing it by going here
Then push the button that says “Install Version from Unity Hub”
It opened my hub then downloaded it despite it not being present.
No need for the new hub if you go this way. Guessing is a local index or something even though its actually accessible. This does for the record work with with hub version 2.2.0
5 Likes
That works - thank you 
Update: the plan is now to release 2.2.1 with the fix today.
You can still download it through the hub link on the beta webpage: unityhub://2019.3.0f1/ffacea4b84e7
1 Like
My Hub just updated to 2.2.1, but still no trace of any 2019.3.
2 Likes
Is there a button for “check for updates” in hub? I am still on 2.2.0
Unity 2019.3.0f1 should now appear again in the Hub. You can quit the hub and restart it to make it refresh the list.
@Charles_Beauchemin @LeonhardP I know that this is out of topic, but Hub 2.2.0/2.2.1 has critical issue about Android NDK. Here is cross-link about issue:
1 Like
I feel that release candidate showing up as full release is a big mistake from Unity Hub team, you guys really should figure out some way to indicate it’s RC and not full release.
Because of the f1 suffix (and Unity hub showing it for some on full release list), people have been posting 2019.3 gotten released everywhere I go on Unity communities and this is hugely misleading for users.
Just having a dedicated page for that version alone that says it’s RC is not enough because most people won’t even open that link in normal conditions (nor many know how to even find that link unless others post it like happened now when Hub lost the RC).
3 Likes
@rz_0lento Isn’t it usually only a couple of days before an RC is promoted to release?
@andybak I can’t remember seeing that ever happening on this current release model Unity has. Even if they turned RC into release for some reason as is, fairly certain it would still get additional f-version for the sake of making it clear to users it’s a full release now.
They haven’t always done RC’s though, like for example 2019.2 didn’t get one but 2019.1 did (Unity 2019.1.0f1).
Release candidates should be named with different suffix. Unity 2019.3rc1. Why do you use “f” - suffix for both release candidate and final release?