Page MenuHomePhabricator

edit conflict yourself by editing same section again
Open, Needs TriagePublicBUG REPORT

Description

Steps to reproduce

  1. edit a section of an article, publish
  2. edit same section again, publish

Expected results

after first save, page display should reflect your own changes. editing again show your own changes in edit mode as well. should be possible to reliably edit several times in one minute. save early and often.

Actual results

after first save return to same content from before edit. edit again and it shows source from before first edit and get edit conflict on save. swipe down to refresh content, now it does show your edit. try again to edit and source still shows old content and get edit conflict popup again.

these are the 2 edits: https://en.wikipedia.org/w/index.php?title=Azlo&dir=prev&offset=20200506213859%7C955270532&limit=2&action=history

caching has been screwy in this app a long time.

see also T66281

Environments observed

App version: Android App 2.7.50320-beta-2020-05-20
Android OS versions: 9
Device model:
Device language: en

Event Timeline

still broken 2.7.50334-beta-2020-11-02

LGoto triaged this task as High priority.Nov 16 2020, 5:22 PM
LGoto moved this task from Needs Triage to Bug Backlog on the Wikipedia-Android-App-Backlog board.

I'm the only editor to that article in more than 48 hrs and following the instructions to refresh and try again doesn't help.

2.7.50336-beta-2020-11-24

jeremyb-phone raised the priority of this task from High to Needs Triage.Dec 16 2020, 7:49 AM

my gut says this is a 5 minute fix for someone that already knows the right part of the codebase. seems there's more than one local cache in the app. a manual refresh immediately after edit updates the rendering but doesn't purge/update the cache used by the in-app editor.

if I'm missing something here please set me straight.

2.7.50337-beta-2020-12-04

got an edit conflict then waited 10+ mins, still was a conflict. (and I was still the only editor today)

then tried something new and found a workaround:
force quit the Wikipedia app and try again and no conflict. need to do more testing to confirm this fixes in all cases. inconvenient but better than nothing.

and now force quit doesn't help. so maybe was a coincidence the first time.