Copyright © 2026 Unity Technologies
Steps to reproduce:
Actual results: Steps 2 and 4 each raise a modal, and a toast carrying the same text
Unable to install The Hub is unable to recognize this archived Editor version. Please try again later. [ Got it ]
Neither link was an install link, and no archived Editor version is involved. The condition is also permanent, so "Please try again later" sends the user into a retry that cannot succeed.
The log records a matching internal warning:
level=warn moduleName=UnityHubProtocolHandler
"Error while trying to fetch data for a custom editor: Error: Missing [Unity] section in ini data"
The split is by route, not by whether the link is an editor link:
| Link | Received | Install error + ini warning |
|---|---|---|
| unityhub:// | Yes | No |
| unityhub://login | Yes | No |
| unityhub://login/callback | Yes | No |
| unityhub://uvcs | Yes | No |
| unityhub://uvcs/foo | Yes | No |
| unityhub://main | Yes | Yes |
| unityhub://main/projects | Yes | Yes |
| unityhub://bogusroute | Yes | Yes |
| unityhub://zzz | Yes | Yes |
Expected results: An unrecognised "unityhub://" route produces a message about the link rather than about installing an Editor, and does not offer a retry when the outcome is deterministic. The routes the Hub handles - login, login/callback, uvcs and bare unityhub:// - already show nothing.
Reproducible with versions: 3.22.0-beta.1
Not reproducible with versions: No other versions tested
Tested on (OS): MacBook Pro - Tahoe 26.6.2
Issues you vote on will appear here