wordpress-mobile / wordpress-mobile/WordPress-Android

Edited post content is not updated in the post details after a pull to refresh

Open
#20,408 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Type] Bug Reader: Post Detail
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

This is to track an internal report in slack (p1709625498462279-slack-C0180B5PRJ4)

We need to confirm if what I was able to replicate actually covers the issue reported, but starting to note it down (hey @joashrajin 👋 , please feel free to integrate or correct what I'm reporting in case 🙇 )

Expected behavior

If I have a post in the reader cache (that is, I opened the post in the post details already), and the author of the post edits the post body, I would expect the body changes to reflect in the post details (at least after a pull to refresh)

Actual behavior

If I have a post in the reader cache (that is, I opened the post in the post details already), and the author of the post edits the post body, I do not see the edited body even if I do a pull to refresh in the post details; but I can see the changes if I:

  • I go to the list of posts of that site in the reader
  • do a pull to refresh in the feed (list of posts)
  • then open the post details again
Steps to reproduce the behavior
  • open a post in the post details screen
  • edit the post body from the web or another instance of the app (so you do not close the post details screen you just opened)
  • try to pull to refresh on the post details screen in the app and check the body changes are not udpated

Note: I was able to replicate this on an atomic site and on a a8c p2

Tested on [samsung S23], Android [Android 14], JPAndroid / WPAndroid [24.3-rc1]

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

No files, tests, or code entry points are named. First reproduce the flow on the listed Android setup: open a post, edit it elsewhere, and pull to refresh in post details. Done means the edited body appears in post details without returning to the site’s post list.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
mobile-dev
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.