wordpress-mobile / wordpress-mobile/WordPress-Android

Comments: the default comment on a new WordPress install doesn't show up in the app when Jetpack is connected

Open
#12,880 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Pri] Low [Type] Bug Comments Jetpack
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

Steps to reproduce:

  1. Set up a new WordPress install, do not make any changes to it.
  2. In the app, log in to WordPress.com.
  3. Add the site from step 1.
  4. Go to Comments and verify you can see the default comment.
  5. Go to Stats and complete the Jetpack install flow.
  6. Go to My Site > Comments.
  7. Try to find the default comment after pull to refresh.

Result: the default comment shows up in the app for a self-hosted site but once Jetpack is install then it disappears. (3m42s) The same comment appears normally in WP Admin and in Calypso.

Tested with WPAndroid 15.6-rc-2 on Pixel 3 Android 10 using `likely-herring.jurassic.ninja` running WordPress 5.5.1. and Jetpack 8.9.

App logs for the timestamp matching the video 
WordPress - 15.6-rc-2 - Version code: 913
Android device name: Google Pixel 3

01 - [Sep-03 16:42 NOTIFS] notifications update job service > all tasks completed
02 - [Sep-03 16:42 NOTIFS] notifications update job service > destroyed
03 - [Sep-03 16:42 STATS] 🔵 Tracked: site_menu_opened, Properties: {"blog_id":182394729,"is_jetpack":true,"menu_item":"comments"}
04 - [Sep-03 16:42 API] Dispatching action: CommentAction-FETCH_COMMENTS
05 - [Sep-03 16:42 UTILS] trackLastActivity, activityId: Comments
06 - [Sep-03 16:42 COMMENTS] load comments task already active
07 - [Sep-03 16:42 API] Dispatching action: CommentAction-FETCHED_COMMENTS
08 - [Sep-03 16:42 API] Dispatching action: CommentAction-FETCH_COMMENTS
09 - [Sep-03 16:42 API] Dispatching action: CommentAction-FETCHED_COMMENTS
10 - [Sep-03 16:42 API] Dispatching action: CommentAction-FETCH_COMMENTS
11 - [Sep-03 16:42 API] Dispatching action: CommentAction-FETCHED_COMMENTS
12 - [Sep-03 16:42 UTILS] trackLastActivity, activityId: My Site
13 - [Sep-03 16:42 API] Dispatching action: AccountAction-FETCH_ACCOUNT
14 - [Sep-03 16:42 API] WhatsNewStore: fetchWhatsNew
15 - [Sep-03 16:42 API] Dispatching action: AccountAction-FETCHED_ACCOUNT
16 - [Sep-03 16:42 STATS] 🔵 Tracked: me_tab_accessed
17 - [Sep-03 16:42 STATS] 🔵 Tracked: support_opened, Properties: {"origin":"ME_SCREEN_HELP"}
18 - [Sep-03 16:42 UTILS] trackLastActivity, activityId: Help Screen
19 - [Sep-03 16:42 UTILS] App goes to background
20 - [Sep-03 16:42 STATS] 🔵 Tracked: application_closed, Properties: {"time_in_main_reader":0,"last_visible_screen":"Help Screen","time_in_reader_paged_post":0,"time_in_app":15,"time_in_subfiltered_list":0,"time_in_reader_filtered_list":0}
21 - [Sep-03 16:42 MAIN] ConnectionChangeReceiver successfully unregistered
22 - [Sep-03 16:55 UTILS] App comes from background
23 - [Sep-03 16:55 STATS] 🔵 Tracked: application_opened
24 - [Sep-03 16:55 READER] notifications update job service > job scheduled
25 - [Sep-03 16:55 API] Dispatching action: SiteAction-FETCH_SITES
26 - [Sep-03 16:55 API] Dispatching action: AccountAction-FETCH_SUBSCRIPTIONS
27 - [Sep-03 16:55 API] Dispatching action: SiteAction-FETCH_SITE
28 - [Sep-03 16:55 API] Dispatching action: SiteAction-FETCH_SITE_EDITORS
29 - [Sep-03 16:55 UTILS] trackLastActivity, activityId: Help Screen
30 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
31 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
32 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
33 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
34 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
35 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
36 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
37 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
38 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
39 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
40 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
41 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
42 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
43 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
44 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
45 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
46 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
47 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
48 - [Sep-03 16:55 POSTS] PageStore: getPagesWithLocalChanges
49 - [Sep-03 16:55 NOTIFS] notifications update job service > created
50 - [Sep-03 16:55 UTILS] Remote config updated: false
51 - [Sep-03 16:55 API] Dispatching action: SiteAction-FETCHED_SITE_EDITORS
52 - [Sep-03 16:55 DB] Site found by (local) ID: 1324
53 - [Sep-03 16:55 DB] Updating site: https://likely-herring.jurassic.ninja
54 - [Sep-03 16:55 API] Dispatching action: SiteAction-FETCHED_SITES
55 - [Sep-03 16:55 DB] *** REDACTED ***
93 - [Sep-03 16:55 API] Dispatching action: SiteAction-UPDATE_SITE
94 - [Sep-03 16:55 DB] Site found by (local) ID: 1324
95 - [Sep-03 16:55 DB] Updating site: https://likely-herring.jurassic.ninja
96 - [Sep-03 16:55 NOTIFS] notifications update service > completed
97 - [Sep-03 16:55 NOTIFS] notifications update job service > all tasks completed
98 - [Sep-03 16:55 NOTIFS] notifications update job service > destroyed
99 - [Sep-03 16:55 API] Dispatching action: AccountAction-FETCHED_SUBSCRIPTIONS

(internal reference & previously related issues: p4a5px-1Nh-p2, https://github.com/Automattic/jpop-issues/issues/633, https://github.com/wordpress-mobile/WordPress-Android/issues/7131 cc @lezama @khaykov)

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

Reproduce the issue through My Site > Comments after completing the Jetpack install flow, using the CommentAction-FETCH_COMMENTS entries in the supplied logs as the initial entry point. Compare comment fetching before and after Jetpack is connected, and consider the issue done when the default comment remains visible after pull to refresh.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.