USAA Direct Connect is Broken Again

[Brendan Coupe]

Sorry, wrong terminology. Builds do not fail, the Direct Connect problem
appears in my builds after December 23. I do not have any builds on Dec 24
& 5.

The error was about username and/or password error.

To be clear, this is the change you made some time last year based on some
work GNUCash had done to get KMM to work on USAA again. I think you added
User Agent and maybe some other tricks. I thought you made this for USAA
accounts only, at least for now.

It's setable in my USAA accounts (set to InetClntApp/3.0) and grayed out on
my other accounts.

*----*
*Brendan Coupe*


On Mon, Jan 3, 2022 at 10:25 AM Thomas Baumgart via KMyMoney-devel <
kmymoney-devel at kde.org> wrote:

> Brendan,
>
> On Montag, 3. Januar 2022 17:26:09 CET Brendan Coupe via KMyMoney-devel
> wrote:
>
> > I just found a version compiled on Dec 23 on my laptop. The problem is
> not
> > present in that version either.
>
> OK, so it seems to be the Dec 26th change then that's causing a bit
> different
> behavior. I tried to find some details on 'Several recent builds have
> failed'
> but did not see a more detail explanation as to what fails. If a build
> fails,
> that usually means, the program does not build. If it is anything else that
> is not working, then I would need much more details about the problem
> itself
> because I still don't understand it.
>
> Thanks in advance. Very much appreciate your QA work there.
>
> Thomas
>
> --
>
> Regards
>
> Thomas Baumgart
>
> https://www.signal.org/       Signal, the better WhatsApp
> -------------------------------------------------------------
> Linux - Life is too short for reboots
> -------------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kmymoney-devel/attachments/20220103/a3dfda7b/attachment-0001.htm>