Toolkit Reports not showing up

[jamesrob21]

When I click on Toolkit Reports it flashes real quick on my screen and then disappears.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. OSX, Windows]
• Browser [e.g. chrome, firefox]
• Toolkit Version [e.g. 2.22.0]

Setting Export Please replace the text 'REPLACE_ME_WITH_SETTINGS' below with your exported Toolkit settings. You can export these by going to the Toolkit Options page, click the Import/Export Settings button at the top right and copying the text in the modal which appears.

Note! DO NOT replace the leading and trailing ``` characters as they are required formatting characters.

REPLACE_ME_WITH_SETTINGS

[Chillers1]

Same thing happening here

[ryandzink]

Same here. I get this in the dev console (Firefox) when I click on Toolkit Reports:

TypeError: expenseMonthData is undefined
    _normalizeNetIncomes moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62905
    _normalizeNetIncomes moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62901
    _calculateData moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62765
    componentDidUpdate moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:62707
    lk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1712
    jk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1711
    ik moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1710
    Xk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1734
    Qk moz-extension://a5dfb303-ceab-498b-bf6d-c1e79e542f83/web-accessibles/ynab-toolkit.js:1732

[tuvmos]

I also have this issue. The Toolkit was working until I used a filter to look at one category by itself. Now it only shows a blank screen. When I click on the Toolkit Reports in the sidebar it momentarily appears for less than a second and then disappears again. I have cleared the cache. I have tried logging out/in of YNAB. I have tried uninstalling/reinstalling Toolkit as well as disabling/abling it - nothing works. Please fix!

[r-uiz]

Having this same exact problem after filtering out a category and changing the months covered. Here are the errors that are raised in the browser console on Arc browser.

TypeError: Cannot read properties of undefined (reading 'total')
    at ynab-toolkit.js:62905:65
    at Array.map (<anonymous>)
    at IncomeVsExpenseComponent._normalizeNetIncomes (ynab-toolkit.js:62901:37)
    at IncomeVsExpenseComponent._calculateData (ynab-toolkit.js:62765:42)
    at IncomeVsExpenseComponent.componentDidUpdate (ynab-toolkit.js:62707:18)
    at lk (ynab-toolkit.js:1712:316)
    at jk (ynab-toolkit.js:1711:446)
    at ik (ynab-toolkit.js:1710:431)
    at Xk (ynab-toolkit.js:1734:96)
    at Qk (ynab-toolkit.js:1732:398)

Toolkit Error:
  - Feature: unknown
  - Feature Setting: unknown
  - Function: global
  - Message: Cannot read properties of undefined (reading 'total') TypeError: Cannot read properties of undefined (reading 'total')
    at chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62905:65
    at Array.map (<anonymous>)
    at IncomeVsExpenseComponent._normalizeNetIncomes (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62901:37)
    at IncomeVsExpenseComponent._calculateData (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62765:42)
    at IncomeVsExpenseComponent.componentDidUpdate (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:62707:18)
    at lk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1712:316)
    at jk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1711:446)
    at ik (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1710:431)
    at Xk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1734:96)
    at Qk (chrome-extension://lmhdkkhepllpnondndgpgclfjnlofgjl/web-accessibles/ynab-toolkit.js:1732:398)

ynab-toolkit.js:62905 Uncaught TypeError: Cannot read properties of undefined (reading 'total')
    at ynab-toolkit.js:62905:65
    at Array.map (<anonymous>)
    at IncomeVsExpenseComponent._normalizeNetIncomes (ynab-toolkit.js:62901:37)
    at IncomeVsExpenseComponent._calculateData (ynab-toolkit.js:62765:42)
    at IncomeVsExpenseComponent.componentDidUpdate (ynab-toolkit.js:62707:18)
    at lk (ynab-toolkit.js:1712:316)
    at jk (ynab-toolkit.js:1711:446)
    at ik (ynab-toolkit.js:1710:431)
    at Xk (ynab-toolkit.js:1734:96)
    at Qk (ynab-toolkit.js:1732:398)

[erebks]

Found a way to recover: On Chrome navigate to the developer toolkit -> Application -> Local Storage and search for: ynab-toolkit-active-report.

Delete this entry and you should be able to use the Toolkit again.

[ryandzink]

Thanks @erebks the same works in Firefox using the dev console there as well.

[lazynooblet]

Thanks @erebks the same works in Firefox using the dev console there as well.

Until we click on Income vs Expense again.

[jamesrob21]

Yes that worked momentarily, but when I click on the "Income vs. Expense" icon it causes the screen to go blank again.

[palermog]

I'm getting the same error here. Fixable in the console, happens again when clicking Income vs. Expense.

[jeffreyrdubois]

in addition to what @erebks suggested, also delete the record found when searching "income-vs-expense-category-filters" this allows you to go back into the income and expenses

[SgtBatten]

Same issue

[WanderingRaven]

Commenting to add mine as well.

I did remember that I was messing around in my data view and selected "none" either in the categories or accounts selector options, not sure which but hopefully that might help narrow it down.

[r-uiz]

in addition to what @erebks suggested, also delete the record found when searching "income-vs-expense-category-filters" this allows you to go back into the income and expenses

This fixes clicking on Income v Expense messing the reports up again. Thanks!

[Bilbyj]

in addition to what @erebks suggested, also delete the record found when searching "income-vs-expense-category-filters" this allows you to go back into the income and expenses

This fixes clicking on Income v Expense messing the reports up again. Thanks!

Issue: I can't find the income-vs-expense-category-filters. I have looked in developer tools for Chrome and FireFox.

I can delete entries for:
FireFox: Application -> Local Storage and search for: ynab-toolkit-active-report Application -> Local Storage and search for: ynab-toolkit-income-vs-expense-collapse-state Chrome: Storage -> Local Storage and search for: reports.spending.totals Storage -> Local Storage and search for: ynab-toolkit-active-report Storage -> Local Storage and search for ynab-toolkit-income-vs-expense-collapse-state

[palermog]

Similar to @Bilbyj, I can't find any of these entries by filtering within Local Storage. Deleting the entire http://app.ynab.com entry in Local Storage works to access Toolkit Reports again, but does not reset Income v. Expense.

[Kevenp1867]

I just reported the same issue today for these reports appearing for a second or less and then disappearing...Help

[willpoorman]

After adding my findings about #3425, I skimmed through a few other reported issues. It appears that #3414, #3430, and #3425 are all reporting the same issue where the Toolkit Reports stop working after the user clicks on the Income and Expenses tab. So, I'm going to post this comment on all 3 so that everyone looking at them knows they're related.

[Jonparkersound]

I'm having the same issue.

[OlegWock]

I believe this problem was fixed and released in v3.13.1, so I'm going to close this issue.

If problem still persist, please feel free to reply and I'll reopen the issue