Help/Foreseenly CashFlow/App Freezing or Crashing
Foreseenly CashFlow - Troubleshooting

App Freezing or Crashing

Quick steps and crash-report help

OS 27: Forecast stops refreshing after Past

On OS 27, opening Past and then returning to Forecast can leave the app stuck, with Forecast no longer refreshing.

A fix is coming in version 1.17.7. In the meantime, if the app gets stuck in Past, open the App Switcher, swipe up on Foreseenly's preview to force-close it, then reopen the app.

Fixed in 1.17.6: crash when changing a plan to Once

In version 1.17.5, changing a plan's frequency to Once could crash Foreseenly. This bug is fixed in 1.17.6.

Update to version 1.17.6 or later. If you are still using 1.17.5, tap Semi first, then tap Once as a workaround.

Try this first

For other freezes, unexpected closures, or problems opening Foreseenly, start with these recovery steps.

  1. Open the App Store and make sure Foreseenly CashFlow is updated.
  2. Close and reopen Foreseenly. Open the App Switcher, find Foreseenly, then swipe up on its preview to close it.
  3. Restart your iPhone or iPad, then open Foreseenly again.
  4. If no Foreseenly update is available, install the latest iOS or iPadOS update.
Before deleting or reinstalling Foreseenly, make sure you have a current backup or contact support. Deleting the app can remove local data stored on the device.

If it keeps happening

Tell QApps what happened so we can investigate. These details help us reproduce the problem:

  • Your device model and iOS or iPadOS version.
  • Your Foreseenly CashFlow version, if you can open the app long enough to check it.
  • What screen you were on and what you tapped before the freeze or crash.
  • Whether it happens every time or only sometimes.

Submit a Foreseenly help ticket or email [email protected].

Send a crash report on iOS 26 or iPadOS 26

If Foreseenly closes unexpectedly, you can choose to send QApps its crash report to help diagnose the problem.

What you share: A crash report typically includes the app and system versions, device model, crash time, and technical details about the failure. It may also contain diagnostic identifiers, file paths, or app-generated error text.

Sharing this report does not send a copy of your Foreseenly database or give support access to your device, iCloud, or bank accounts. Do not attach financial backups or bank exports.

If you email the report, QApps receives your email address, any sender name, your message, and the attachments you choose to send.

  1. Open Settings on your iPhone or iPad.
  2. Go to Privacy & Security > Analytics & Improvements > Analytics Data.
  3. Look for a report named Foreseenly or CashFlow with a date and time matching the crash.
  4. Open the report, tap the Share icon (a square with an upward arrow), choose your email app, and send the report to [email protected].

No matching report? You can still contact support with the steps that caused the problem. A freeze does not always produce a crash report.

Optional: share analytics with developers

In Settings > Privacy & Security > Analytics & Improvements, you can enable Share iPhone Analytics (or Share iPhone & Watch Analytics), then Share With App Developers if available. On iPad, look for Share iPad Analytics.

This setting is optional, applies to apps generally, and reports may not appear immediately. Apple says the information it shares with developers is aggregated or provided in a form that does not personally identify you. You can turn off Share With App Developers at any time. To send only one Foreseenly report, use the manual method above.

More information: Apple: sharing analytics, Apple: what a crash report contains and App Analytics & Privacy.

Need more help? Search this product's help articles, share a product idea, or send a ticket if you still need help.

Was this article helpful?

Your vote helps QApps find articles that need clearer steps or better screenshots.

What was missing?

Submit help ticket