Skip to main content

Report a problem

Use the in-app feedback flow when something in Big Picture Money does not work as expected.

Prerequisites​

  • Big Picture Money is installed and open.
  • You have an email address for follow-up.

Steps​

  1. In the title bar, click the Help icon.
  2. Choose Report an issue.
  3. On the first screen, choose Report a problem, then click Continue.
  4. Enter a short title that summarizes the issue.
  5. Describe what happened. Optionally add what you expected and steps to reproduce.
  6. Enter your contact email (required). It is used for follow-up only.
  7. Optionally attach screenshots or check Include app logs to attach recent diagnostic log lines.
  8. Review the diagnostics the app will include (version, operating system, build channel, and current page).
  9. Click Submit report.

From Home Action required​

When the app has logged errors that have not been reported yet, Home Action required may include Report errors (even if anonymous usage sharing is off).

  1. On Home, open Action required → Report errors.
  2. Review the listed errors and what will be included.
  3. Click Send error report to open the normal issue report flow with those errors prefilled.
  4. Complete contact email and submit as usual.
  5. Optional: choose Never ask me to report issues again to hide future prompts (re-enable under Settings → General → Ask me to report app errors).

From a failed screen​

If a page fails to load, the main content area shows a short message that something went wrong (not a raw technical dump). The sidebar and title bar stay usable.

  1. Optionally click Back to return to the previous page, or use the sidebar or title bar to open another section.
  2. On the failed screen, click report this issue.
  3. Review the prefilled title and description (they include error detail from the failure), add your contact email, and submit as usual (or edit the text first).

Expected result​

  • Help → Report an issue opens the feedback dialog.
  • The first screen offers problem, feature, documentation, and security choices.
  • A contact email is required before submit.
  • The review step shows diagnostics without account balances or transaction details.
  • After a successful submit, you see a reference id such as BPM-ISSUE-123 to use when you follow up with support.
  • Report errors from Action required opens a review modal, then the same submit flow; after a successful send those errors no longer appear under Action required.
  • A failed screen keeps navigation available, offers Back, and offers report this issue into the same feedback flow with error details prefilled for review in that dialog (not shown as a dump on the failed screen itself).