wordpress-mobile / wordpress-mobile/WordPress-iOS

Followers Total shows incorrect count

Open
#23,110 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug Stats
Dominant language
Swift
Stars
3.9k
Forks
1.2k
Avg merge
23h 51m
Merged PRs (30d)
58

Description

Expected behavior

The Total Follower card in Stats Insights sometimes shows a number that excludes "email followers". For example, if the site has 10K followers in total (8K WP.com followers and 2K email followers), the Total Followers card should show 10K but sometimes shows 8K.

Actual behavior

A lower count is shown.

Steps to reproduce the behavior
  1. Open Stats on a high-traffic site for best results
  2. Add the Total Followers card if it's not already shown
  3. Notice that sometimes its value is not correct and that is because it sometimes excludes email followers
  4. Try again until you see the error
  5. Notice that pull-to-refresh may fixe the error

The app should use the v2/sites/{site_id}/subscribers endpoint according to pejTkB-1l5-p2#comment-1315, which includes a total:

{
  "total": 3,
  "pages": 1,
  "page": 1,
  "per_page": 100,
...
}

Note: there's a known issue with this endpoint on high-traffic sites: pejTkB-1l5-p2#comment-1318

Tested on iPad simulator, iOS 17.2, Jetpack iOS trunk

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the Stats Insights implementation for the Total Followers card and inspect how it obtains the follower count. Compare its data source with the v2/sites/{site_id}/subscribers endpoint and its total field, then reproduce on a high-traffic site using the listed iPad simulator setup. Done means the card consistently includes email followers and handles the endpoint's known high-traffic limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
swift
Domain
analytics
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.