Strange basic auth behaviour in 2026.1.2

We are using Yaak to successfully work with a public API. One end point redirects to Amazon s3 after auth to return a file and this now fails. It did work in 2026.1.1

I do not know if it is related to another issue we have with Yaak and authentication on this API. It authenticates on Basic auth with the api key going in the username field and a blank password field (eg ‘apikey:’). When creating a new request in Yaak it will never work first time until you have either entered and removed text in the password field for Basic auth or set an env in there such as PASSWORD and left the value blank in Environment variables.

Curl requests copied out from these broken Yaak requests match identically those that work and if imported also require manipulation of the password field/textbox. Duplicated requests within Yaak work first time.