Applies to: Quicken Classic mobile companion app on iPad (requires an active Quicken Classic desktop subscription for full sync). This article does not cover Quicken Simplifi.
- Quicken tries to sync your data immediately after Face ID succeeds
- An outdated app, corrupted cache, or unstable sync connection interrupts that handoff
- Updating the app, clearing the cache, and re-authenticating typically resolves it
If your Quicken app opens fine, shows the Face ID prompt, and then closes itself the moment you’re authenticated, you’re not imagining it. This is a recognized pattern among Quicken mobile users on iPad — see how to fix Quicken login errors on mobile for related login issues — and in most cases it’s tied to how the app briefly reloads your data right after biometric login. When that reload process gets interrupted or overloaded, the quicken app crashing instead of landing you on your dashboard.
This issue tends to show up more often after an iPadOS update, a Quicken app update, or when the connected data file is unusually large or has a sync conflict in the background. The good news is that this is almost always fixable without losing any financial data, since the Quicken Classic mobile app is a companion app that syncs with your Quicken Classic desktop data file — it isn’t your only copy of your data.
Below is a clear breakdown of why this happens and how to fix it, step by step.
Why This Happens
In many cases, this crash isn’t related to Face ID itself; it’s related to what happens right after Face ID succeeds. Once you’re authenticated, Quicken tries to:
- Verify your session token
- Pull the latest synced data
- Rebuild your dashboard view
If any of these steps takes too long, times out, or hits a corrupted local cache file, the app can crash rather than freeze or show an error. This usually happens when the iPad is running low on background memory, the Quicken app version is outdated, or there’s a temporary sync conflict between the mobile app and your Quicken desktop data — a related issue covered in Quicken won’t sync on iPad.
Quick Fix
- Force close the Quicken app completely
- Confirm your iPad has the latest iPadOS update installed
- Update Quicken from the App Store if an update is available
- Reopen the app and log in again with Face ID
- If it crashes again, restart the iPad before trying once more
If the crash stops after these steps, no further action is needed.
Step-by-Step Solution
Step 1: Force close and clear the background session
Swipe up (or double-click the home button on older iPads) to view open apps, then swipe Quicken away completely. This clears any stuck background process that may be interfering with the Face ID handoff.
Step 2: Check for iPadOS updates
Go to Settings > General > Software Update. An outdated iPadOS version can cause compatibility issues with how Quicken handles biometric authentication.
Step 3: Update Quicken to the latest version
Open the App Store, search for Quicken, and check if an “Update” button appears instead of “Open.” App updates often include fixes for exactly this kind of login crash. You can also check current app details on Quicken’s official mobile support page.
Step 4: Sign out and back in (soft reset)
Open the app’s account/profile menu and sign out, then sign back in with your Quicken ID. This forces Quicken to rebuild your session cleanly instead of relying on a potentially corrupted cached one. (Exact menu wording may vary slightly by app version — look for an Account or Profile icon within the mobile app settings.)
Step 5: Reinstall the app if the crash continues
Delete the Quicken app and reinstall it from the App Store. Because the mobile app is a companion to your Quicken Classic desktop data file and syncs through Quicken’s servers, this does not delete your financial records — it only clears the local app cache. Once reinstalled, log in with your usual Quicken ID and re-enable Face ID.
Caution: Before reinstalling, confirm your desktop Quicken file has synced recently. If you rely solely on the mobile app without a desktop file, back up your data through your account settings first.
Advanced Fix (For Persistent Crashes)
If the app still crashes after reinstalling, the issue may be tied to a larger data file or an unresolved sync conflict on Quicken’s servers. In this case:
- Try logging in on a different device (like a phone) to confirm whether the account syncs normally elsewhere
- If it works on another device but not the iPad, the issue is local to that device’s cache rather than your account
- Restarting the iPad fully (not just closing the app) can also clear temporary memory conflicts that a simple force-close won’t resolve
If the crash still isn’t resolved after trying these advanced steps, visit Quicken’s mobile app support and contact page to reach their team directly.
Prevention Tips
- Keep both iPadOS and the Quicken app updated regularly
- Avoid force-closing Quicken mid-sync, as this can leave cached data in an inconsistent state
- Restart your iPad occasionally to clear background memory buildup — persistent freezing issues are covered separately in Quicken app keeps freezing: troubleshooting guide
- If you manage a large data file, sync your desktop Quicken file regularly to keep the mobile app’s cache current
If you’re still running into sync hiccups after working through this guide, our related Quicken mobile troubleshooting articles below can help you resolve them quickly.
Frequently Asked Questions —
No. The Quicken Classic mobile app is a companion to your desktop data file and syncs through Quicken’s servers, so reinstalling the app only clears local cache — it does not erase your records.
It’s not necessarily Face ID-specific — password logins can trigger the same crash if the underlying sync or cache issue is present. Face ID logins just tend to complete faster, which sometimes surfaces the timing issue more visibly.
It can occur on any model, though it’s reported more frequently on older iPads with limited background memory, or on any device running an outdated iPadOS version.
In most cases, it’s a device-level app cache issue rather than an account problem, especially if the account logs in fine on another device.
That’s usually a separate iOS permissions issue. Check Settings > Face ID & Passcode, and confirm Quicken is toggled on under the list of apps allowed to use Face ID.