Problems with Analytics and Subcategories

I have spent a long time piecing together how this problem (or problems?) manifests itself. It was very confusing but here is my breakdown I started using the app in Oct 25 (with an Ultimate subscription) which may be relevant to the description of the bug. I use an iPad running iOS 16.7.12 and an iPhone running iOS 18.6.2. The error(s) occurs on both.

There seem to be four distinct but related parts so I will describe them separately to help understanding. In all of these cases, I simply want to view the totals for categories and possibly subcategories in a month so I start by doing the following in all of them:

I select Analytics on the Feed page, and then select the month I want by swiping the bar chart image right or left (the direction I swipe depends on which month I want) and then I click on one of the category totals. Here are the problems…

  1. The problem I describe here in (1) affects any month, including the current month.

Sometimes (definitely not always) when I select a month and then click on a category total, the bar chart at the top of the category’s screen doesn’t show the selected month (nor any subcategory totals).

If I back-up a level and then re-select the category, the right month is now highlighted on the bar chart and subcategory totals (if any) are displayed.

  1. I believe the problem I describe here in (2) doesn’t occur for the current month and the preceding three months. It’s Oct 25 now, so the problem definitely occurs when I look at months earlier than July 25.

Let’s say I choose June 25. The totals for the categories in June 25 are displayed as expected. I then click on one of the category totals to see its transactions and its subcategory totals. I then click on one of the subcategory totals and view its transactions. So far so good.

I then back-up one level to the category’s screen and suddenly the highlighted month on the bar chart jumps to a month earlier (May in this example). After this event happens, problems tend to get worse (but i don’t think this specific error is a prerequisite for the following issues).

  1. Instead of June 25, let’s say I choose an even earlier month, say March 25.

The totals for the categories in March 25 are displayed as expected. I then click on one of the category totals to see its transactions and this is where another part of the bug occurs.

The bar graph at the top of the category’s screen now shows I have selected one of the months either side of the month I actually chose. So in my example, instead of March being highlighted, either February or April is highlighted. Which one is highlighted seems to depend on the direction I was swiping when I first selected March.

The transactions listed are actually for my chosen month, March in this example (except for the subcategories, which is a problem covered in (4)).

If I back-up and re-select the category, then the bar chart on the category’s screen usually now shows the correct month (March in this example).

  1. I believe from my tests that the following problem doesn’t happen if I am looking at the current month or any of the preceding six months. It’s Oct 25 now, so for months that are earlier than April 25 the problem definitely does occur.

When I select a category total in a month to look at, as I have described in all of the above, then subcategory totals are displayed but they are for a later month (for example, if I have selected January 25 then I might see subcategory totals for June 25!).

If I click on a subcategory total, then I will be shown the transactions for that later month (June 25, despite having selected January 25).

1 Like

Hi @JeffRUK,

thanks for reporting this - we are getting an engineer on it!

When looking at a month’s transactions in Analytics, sometimes the totals for the subcategories that have been assigned in that month do not appear, by which I mean the subcategories and totals that usually show up under the Manage subcategories heading are not displayed. It seems to be an intermittent fault that occurs quite frequently.

Hi @JeffRUK
Thanks for bringing this issue to our attention! So that we can take a look at this for you can you please take a screen recording of this issue and reach out to me via our live chat :slight_smile:

Hi. I have actually created a more comprehensive topic on this bug.

Hey guys - thanks for reporting this.

We had an engineer looking into the issue on Friday and he has fixed it; you should get the fix in the next app update. :slight_smile: