Repository navigation
installer fails to find archives for release candidates without the a/b prefixes #167
Description
VERBOSE: GET https://unity3d.com/get-unity/download/archive with 0-byte payload
VERBOSE: received -1-byte response of content type text/html; charset=utf-8
VERBOSE: Attempting version search with builtin_shaders fallback
VERBOSE: GET https://unity3d.com/get-unity/download/archive with 0-byte payload
VERBOSE: received -1-byte response of content type text/html; charset=utf-8
Could not find archives for Unity version 2019.1.0f1
At C:\Users\VssAdministrator\Documents\WindowsPowerShell\Modules\UnitySetup\5.1.115\UnitySetup.psm1:397 char:13
+ throw "Could not find archives for Unity version $Version ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Could not find ...sion 2019.1.0f1:String) [], RuntimeException
+ FullyQualifiedErrorId : Could not find archives for Unity version 2019.1.0f1
##[error]PowerShell exited with code '1'.
Activity
StephenHodgson commentedon Apr 11, 2019
I believe the hubs are using some other way to find and discover availible versions to download.
Might be worth checking out these alternative download methods.
Looks like Unity hasn't posted 2019.1.0f1 on the archives yet, but it's still availible via hub
jwittner commentedon Apr 12, 2019
For some reason 2019.1.0f1 is only available via the beta pages. I think this is confusing UnitySetup, which uses the f/b/p to determine where to go look for a version. Sigh.
[-]installer fails to find archives for 2019.1.0f1[/-][+]installer fails to find archives for release candidates without the a/b prefixes[/+]StephenHodgson commentedon Apr 17, 2019
Seems like the RCs follow a different naming scheme which is breaking it. Likely affects all RCs that are in the beta channel.