wordpress-mobile / wordpress-mobile/WordPress-Android
History: Initial revision is not recorded
Open
Nobody has claimed this yet.
[Pri] Medium
[Type] Bug
Posting/Editing
Revisions / History
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Related:
- https://github.com/Automattic/wp-calypso/issues/64963
- https://github.com/wordpress-mobile/WordPress-iOS/issues/19150
Expected behavior
- The initial revision exists in the app and on the web
- The behavior matches the web
Actual behavior
- The initial revision is lost and only the second revision and after are recorded
Steps to reproduce the behavior
This test was conducted on a .com site.
1. Create a new post in the app, add content, and publish it or save it as a draft
- When tapping ... at the top right in the post, and tapping "History", nothing shows in the list
- On the web, the "Revisions" section for the post doesn't appear
2. Make changes to the post and tap Update
- When tapping ... at the top right, tapping "History" shows one item containing the changes from step 2
- On the web, the "Revisions" section for the post doesn't appear (it may currently hide the section if the count <= 1)
3. Make changes and tap Update
- When tapping ... at the top right, tapping "History" shows two items containing the changes from steps 2 and 3
- On the web, the "Revisions" section is available for the post and shows changes from steps 2 and 3
Tested on Pixel 4a, Android 12, WPAndroid 20.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in the Android app using the History menu and the three-step post editing flow described in the report. Compare the initial save or publish with later updates and verify behavior against the web; done means the initial revision appears in the app and on the web, matching the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100