QFX import is broken (on Sequoia)

caram

Either since I updated to QM 7.9.1, or since upgrading to Sequioa - I don't know which, since I did both at about the same time -, QFX import is broken.

This is a show stopper for me.

Steps to reproduce:

1. File/Import/QFX
2. Select .qfx file
3. A dialog box appears "Updating…", which takes several minutes to terminate
4. If I press "Cancel" at that time, QM networking functions seem broken. I can no longer reimport (nothing happens) or report a problem (nothing happens either)
5. If I am patent enough to let the "Updating…" (updating what?) finish, eventually the usual "Processing 34 transactions…" dialog box appears. It again takes several minutes to terminate.
6. After several minutes, an "Unknown institution" dialog box appears. And then, after I click "OK"…
7. … a "Download unavailable! (request timed out)" dialog box appears.
8. No transaction has been imported.

What should happen:

If have been importing QFX files for years without any problems and it's always been very quick and there has never been a "Unknown institution" (why should it care by the way?) or "Download unavailable!" error.

I am wondering why does QM make network requests when importing a local QFX file. I would expect QM to import the transactions that I ask it to import, irrespectively of the content of the transactions (as long as the file format is OK).

caram

Looking at OFX log file, it seems that the last successful import was on Sep 7.
QM 7.9.1 was already installed at that time, so this does not seem to be the issue.

Now I'm on Sequoia and it no longer imports.

In the OFX.txt file, here's the reported error:

{{-[5]-
2024-09-14 16:24:38 +0000: Got an error, description:
Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x600002aea370 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask <2D83E388-989E-4663-B487-89ED4D697F5E>.<9>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask <2D83E388-989E-4663-B487-89ED4D697F5E>.<9>"
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://ofx-prod-brand.intuit.com/qm2400/fib.dll, NSErrorFailingURLKey=https://ofx-prod-brand.intuit.com/qm2400/fib.dll, _kCFStreamErrorDomainKey=4}
}}-[5]-

The Console.txt file has multiple errors. In particular, it no longer seems to be able to report bugs:

2024-09-14 18:00:27.582 Quicken[76883:1544604] +[IMKClient subclass]: chose IMKClient_Legacy
2024-09-14 18:00:27.582 Quicken[76883:1544604] +[IMKInputSession subclass]: chose IMKInputSession_Legacy
2024-09-14 18:00:38.155 Quicken[76883:1544659] Failed to send sessions to Bugsnag: Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={_kCFStreamErrorCodeKey=-2102, NSUnderlyingError=0x600001ded8c0 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "(null)" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalUploadTask <CFB46C5D-3472-4DC2-8D4F-A14E20685B2C>.<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalUploadTask <CFB46C5D-3472-4DC2-8D4F-A14E20685B2C>.<1>"
), NSLocalizedDescription=The request timed out., NSErrorFailingURLStringKey=https://sessions.bugsnag.com/, NSErrorFailingURLKey=https://sessions.bugsnag.com/, _kCFStreamErrorDomainKey=4}
2024-09-14 18:01:26.707 Quicken[76883:1544604] ERROR: Could not import file: /Users/comptes/Downloads/bankin.qfx
2024-09-14 18:01:26.725 Quicken[76883:1544604] Sparkle update was aborted with error: Error Domain=SUSparkleErrorDomain Code=1002 "An error occurred in retrieving update information. Please try again later." UserInfo={NSLocalizedFailureReason=The request timed out., NSUnderlyingError=0x6000002442a0 {Error Domain=NSURLErrorDomain Code=-1001 "The request timed out." UserInfo={NSUnderlyingError=0x600001d130f0 {Error Domain=kCFErrorDomainCFNetwork Code=-1001 "The request timed out." UserInfo={NSErrorFailingURLStringKey=https://download.quicken.com/mac/Quicken/001/Release/031A96D9-EFE6-4520-8B6A-7F465DDAA3E4/appcast.xml?timestamp=2024-09-14T16:00:23Z&bundle_identifier=com.quicken.Quicken&bundle_version=709.54540.100, NSErrorFailingURLKey=https://download.quicken.com/mac/Quicken/001/Release/031A96D9-EFE6-4520-8B6A-7F465DDAA3E4/appcast.xml?timestamp=2024-09-14T16:00:23Z&bundle_identifier=com.quicken.Quicken&bundle_version=709.54540.100, _kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4, NSLocalizedDescription=The request timed out.}}, NSErrorFailingURLStringKey=https://download.quicken.com/mac/Quicken/001/Release/031A96D9-EFE6-4520-8B6A-7F465DDAA3E4/appcast.xml?timestamp=2024-09-14T16:00:23Z&bundle_identifier=com.quicken.Quicken&bundle_version=709.54540.100, NSErrorFailingURLKey=https://download.quicken.com/mac/Quicken/001/Release/031A96D9-EFE6-4520-8B6A-7F465DDAA3E4/appcast.xml?timestamp=2024-09-14T16:00:23Z&bundle_identifier=com.quicken.Quicken&bundle_version=709.54540.100, _kCFStreamErrorDomainKey=4, _kCFStreamErrorCodeKey=-2102, NSLocalizedDescription=The request timed out.}}, NSErrorFailingURLKey=https://download.quicken.com/mac/Quicken/001/Release/031A96D9-EFE6-4520-8B6A-7F465DDAA3E4/appcast.xml?timestamp=2024-09-14T16:00:23Z&bundle_identifier=com.quicken.Quicken&bundle_version=709.54540.100, NSLocalizedDescription=An error occurred in retrieving update information. Please try again later.}

Quicken Jasmine

Hello @caram,

Thank you for taking the time to visit the Community to report this issue, though we apologize that you are experiencing this.

I have forwarded this issue to the proper channels to have this further investigated. In the meantime, we request that you please navigate to Help > Report a problem and submit a problem report with log files, a sanitized data file, and screenshots (if possible) attached to contribute to the investigation.

While you will not receive a response through this submission, these reports will help our teams further investigate the issue.

We apologize for any inconvenience! Thank you.

Quicken Jasmine

Hello @caram,

Are you still experiencing issues and requiring assistance? If so, please let me know once you have submitted your log files.

Thanks!

caram

Hello @Jasmine,

Sorry for the late response, I have been travelling.

Yes, I am still experiencing the issue. But worse, it also affects reporting a problem (submitting logs) - i.e. the usual dialog box does not appear.

Is there another way I can send the log files?

And BTW I don't think it's related to my data files but to the newly released macOS Sequoia (which I believe your teams have already been working with since June?).

caram

I believe it's the whole of QM networking which is broken on Sequoia.

Quicken_ChrisC

Hello!

Yes, there are many thousands of Quicken customers successfully using Quicken 7.9.1 (and earlier versions) on macOS Sequoia, including the Quicken engineering teams.

Are you using the macOS firewall (search for "firewall" in System Settings) or a VPN or a proxy server or a utility like Little Snitch or similar? If so, they may be misconfigured? For troubleshooting macOS networking issues on Sequoia, Apple Support might be your best bet. But Quicken Support agents are excellent problem solvers, so calling phone support (so you can change network settings, reboot, etc) is a good option too.

caram

Hello!

There seems to be a widespread issue with the firewall on Sequoia:

https://mjtsai.com/blog/2024/09/18/macos-firewall-regressions-in-sequoia/

There was a rule in my firewall for QM to NOT accept any incoming connection (which never caused any issue in previous version of macOS). This rule CANNOT be edited in Preferences/Network/Firewall on Sequoia.

The following shell command changed the rule from Disallow to Allow incoming connections, but this did not solve the QM networking issue:

/usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Quicken.app

Turning off the macOS builtin firewall made QM networking functional again, and as a side effect, QFX files could be imported. Of course, turning off the builtin firewall should be a temporary measure only.

caram

There is a question as why would QM need to accept incoming connections. It sounds like a possible security hole.