Dnia poniedziałek, 3 października 2016 08:20:01 CET Thomas Baumgart pisze:
> Hi,
>
> On Monday 03 October 2016 02:33:49 jef...@outlook.com wrote:
> > On Sunday, October 2, 2016 9:31 PM, Jack wrote:
> > > I could see the clientuid box on the ofx details page, I couldn't enter
> > > anything
> >
>
On 2016.10.03 02:20, Thomas Baumgart wrote:
Hi,
On Monday 03 October 2016 02:33:49 jef...@outlook.com wrote:
> On Sunday, October 2, 2016 9:31 PM, Jack wrote:
> > I could see the clientuid box on the ofx details page, I
couldn't enter
> > anything
> If the box cannot be edited, it seems th
Hi,
On Monday 03 October 2016 02:33:49 jef...@outlook.com wrote:
> On Sunday, October 2, 2016 9:31 PM, Jack wrote:
> > I could see the clientuid box on the ofx details page, I couldn't enter
> > anything
> If the box cannot be edited, it seems that the KMM build did not recognize
> that libofx
On Sunday, October 2, 2016 9:31 PM, Jack wrote:
> I could see the clientuid box on the ofx details page, I couldn't enter
> anything
If the box cannot be edited, it seems that the KMM build did not recognize that
libofx supports CLIENTUID, and so disabled the box. And if that's true, then
eve
On 2016.10.02 16:47, Jack wrote:
I finally managed to install libofx-0.9.11. Running cmake on KMM git
head from the 4.8 branch says yes to both libofx and using
clientuuid. Unfortunately, when I try to map my Chase account, I
just get the error about needing to confirm the account at the C
