I was away so I could not look at this until now.
All of my systems were on versions I compiled before Dec 26 and after the
previous changes earlier in December. USAA import was working. As a
reminder, USAA imports failed on all 3 Fedora 35 systems when KMM was
compiled after Dec 26. On at least o
Hi Brendan,
no, no changes at all on our side since Dec 26th.
See https://invent.kde.org/office/kmymoney/-/commits/5.1
Strange, maybe USAA DC changed something on their side :)
Thomas
On Dienstag, 4. Januar 2022 05:35:30 CET you wrote:
> Did you change anything? I recompiled tonight to get th
Did you change anything? I recompiled tonight to get the error message and
USAA Direct Connect is working. This happened on 3 different systems but I
can only test one until the weekend.
**
*Brendan Coupe*
On Mon, Jan 3, 2022 at 10:47 AM Thomas Baumgart wrote:
> On Montag, 3. Januar 2022 1
On Montag, 3. Januar 2022 18:33:14 CET Brendan Coupe wrote:
> 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 only change that was added in that time frame is
https://invent.kde.org/o
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
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 t
I just found a version compiled on Dec 23 on my laptop. The problem is not
present in that version either.
**
*Brendan Coupe*
On Mon, Jan 3, 2022 at 9:24 AM Brendan Coupe wrote:
> Luckily I compile fairly often and have not deleted some of my recent
> builds.
>
> I am using the 5.1 branch.
Luckily I compile fairly often and have not deleted some of my recent
builds.
I am using the 5.1 branch.
The problem is not present in the version I compiled on Dec 19. I think
this points to the Dec 26 change.
**
*Brendan Coupe*
On Mon, Jan 3, 2022 at 12:53 AM Thomas Baumgart via KMyMoney
Brendan et al,
Happy New Year to all of you. These are not good news to start the year with,
though.
More below.
On Montag, 3. Januar 2022 02:47:16 CET Brendan Coupe via KMyMoney-devel wrote:
> It appears that something has changed recently that has broken the fix that
> Thomas made to get USAA
It appears that something has changed recently that has broken the fix that
Thomas made to get USAA direct connect to work.
Several recent builds have failed. I reinstalled a build from 2021.12.07
and it works fine.
**
*Brendan Coupe*
10 matches
Mail list logo
