Where do you get that build? I suspect it does not have Thomas's latest changes for USAA but I don't remember the error I got before this was working. I compile from the latest 5.1 branch so I know it works with it.
On Sat, Sep 18, 2021, 2:17 PM El Cas <eaglex...@gmail.com> wrote: > I get it after entering all the information to retrieve my accounts. > > I am using the latest commit nightly build (972) > > > On Sat, Sep 18, 2021, 13:59 Brendan Coupe <bren...@coupeware.com> wrote: > >> At what point are you getting that error message? Is it after entering >> the financial institution information manually or after you enter the >> login details and click the next button? >> >> What version of KMM are you using? Did you compile from source >> recently? I'm not sure if this is in the App Image builds yet. >> >> ---- >> Brendan Coupe >> Delta, it's not just a crappy airline. >> If Bill Gates put microchips in the vaccine, you would >> have to go in for an update the second Tuesday of every month. >> On Sat, Sep 18, 2021 at 11:02 AM El Cas <eaglex...@gmail.com> wrote: >> > >> > I used Chrome and got the same results. >> > >> > Am I supposed to run the moneydance scripts? >> > >> > Steps I followed: >> > 1. Went to https://www.usaa.com/accessid >> > 2. Got the client_id from the uri >> > 3. Logged in and authorized >> > 4. Got the Access ID and Access PIN >> > 5. changed client_id to Uppercase >> > 6. Populated the fields in the import process as stated in the original >> email. >> > >> > I get html response instead of OFX response. >> > >> > On Wed, Sep 15, 2021 at 9:50 PM Brendan Coupe <bren...@coupeware.com> >> wrote: >> >> >> >> Try a different browser. The new parts of USAA.com no longer work with >> >> Firefox. I used Brave for USAA. I think Chrome will also work. >> >> >> >> ---- >> >> Brendan Coupe >> >> Delta, it's not just a crappy airline. >> >> If Bill Gates put microchips in the vaccine, you would >> >> have to go in for an update the second Tuesday of every month. >> >> >> >> On Mon, Sep 13, 2021 at 7:35 PM El Cas <eaglex...@gmail.com> wrote: >> >> > >> >> > I followed all the indicated steps but all I got was an html >> response. >> >> > >> >> > Console output >> >> > Starting eventloop >> >> > OfxHttpRequest::slotOfxConnected >> "/home/eagleboy/.local/share/kmymoney/response.ofx" >> >> > Finishing eventloop >> >> > Ending eventloop >> >> > LibOFX ERROR: libofx_detect_file_type(): Failed to identify input >> file format >> >> > LibOFX ERROR: libofx_proc_file(): Could not detect file format, or >> unsupported file format; aborting. >> >> > >> >> > >> >> > Response >> >> > <html> >> >> > <head> >> >> > <META NAME="robots" CONTENT="noindex,nofollow"> >> >> > <script >> src="/_Incapsula_Resource?SWJIYLWA=5074a744e2e3d891814e9a2dace20bd4,719d34d31c8e3a6e6fffd425f7e032f3"> >> >> > </script> >> >> > <body> >> >> > </body></html> >> >> > >> >> > On Sun, Sep 12, 2021 at 5:46 PM Brendan Coupe via KMyMoney-devel < >> kmymoney-devel@kde.org> wrote: >> >> >> >> >> >> I have been working with Thomas Baumgart trying to get KMM direct >> >> >> connect to work with USAA again. Luckily GnuCash was able to get >> >> >> direct connect working with USAA via AqBanking. Based on their >> >> >> success, Thomas was able to determine what was needed in KMM in >> order >> >> >> to get the ofximporter to work with USAA. >> >> >> >> >> >> First, this only works with a newly compiled version of the 5.1 >> branch >> >> >> of KMM. I have some build scripts that you can download here if you >> >> >> would like to try building KMM from source: >> >> >> >> https://drive.google.com/drive/folders/1sfo2HgzaCCSb3d7pjl3To50yoQT5BaXM >> >> >> >> >> >> The next step is to follow the instructions here: >> >> >> >> >> >> >> https://infinitekind.tenderapp.com/kb/online-banking-and-bill-pay/connecting-with-usaa >> >> >> >> >> >> When you complete these steps, USAA should provide you with an >> ACCESS >> >> >> ID, ACCESS PIN, and client_id. This corresponds to User Name, >> Password >> >> >> and Client UID in the ofximporter settings in KMM. You must convert >> >> >> the client_id to UPPER CASE. You can do this in Linux with the >> >> >> following command (substitute your actual client id for client_id): >> >> >> >> >> >> echo client_id | tr '[a-z]' '[A-Z]' >> >> >> >> >> >> Go to the ledger for the USAA account that you want to map and >> select >> >> >> "Map account..." from the Account menu. Select "ofximporter". If >> that >> >> >> is not an option, select "Configure KMyMoney" from the Settings menu >> >> >> and make sure the "OFX Importer" is enabled in the Plugins section. >> >> >> >> >> >> In the first OFX Importer configuration window, click the Manual >> tab. >> >> >> Enter the following information for USAA: >> >> >> >> >> >> ORG: USAA Federal Savings Bank >> >> >> FID: 67811 >> >> >> Server URL: >> https://df3cx-services.1fsapi.com/casm/usaa/access.ofx >> >> >> HTTP User Agent: InetClntApp/3.0 >> >> >> >> >> >> Click the next button. >> >> >> >> >> >> Enter your User Name (ACCESS ID), Password (ACCESS PIN) and Client >> UID >> >> >> (all upper case) that you received from USAA. >> >> >> >> >> >> Check "Store Password" if you want KMM to store your password. Set >> >> >> "Identify As" to "Quicken Mac (Expert)" and enter 2300 in the box >> that >> >> >> just appeared (Application Version). Change the header version from >> >> >> 102 to 103. Click the "Next" button. If you did everything >> correctly, >> >> >> KMM will display a list of accounts that you have at USAA. Select >> the >> >> >> appropriate account and you should be done. >> >> >> >> >> >> This code is brand new. It has been working for me as of today. >> Please >> >> >> make sure you backup your KMM file before you experiment with this >> new >> >> >> code. >> >> >> >> >> >> I know this frustrated other KMM users when USAA made big changes >> late >> >> >> last year. I hope this helps. Please let me know if you have any >> >> >> questions or find any errors in my instructions. >> >> >> >> >> >> ---- >> >> >> Brendan Coupe >> >> >> Delta, it's not just a crappy airline. >> >> >> If Bill Gates put microchips in the vaccine, you would >> >> >> have to go in for an update the second Tuesday of every month. >> >
