wordpress-mobile / wordpress-mobile/WordPress-Android

My Site Dashboard: Updated Avatar not shown on app relaunch

Open
#15,560 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

[Pri] Low [Type] Bug /My site My Site Dashboard
Dominant language
Kotlin
Stars
3.2k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
69

Description

Expected behavior

Avatar maintains updated photo after swipe-off/relaunch sequence

Actual behavior

From @ParaskP7 in PR #15554
I tested the solution thoroughly and what I discover is that there exist a bug with the previous, and of course, the current implementation of CurrentAvatarSource. When you initially update the avatar it is uploaded okay. However, when you update it again, it no longer updates. It seems to be updating, you will see the change indeed, but if you swipe-off and relaunch the app, not just backgrounding and foregrounding it, then you will notice that the avatar hasn't been updated. To recover from that state one would need to log-out and log-in again. Also, it seems that any update it taking about 2-3' mins to actually take effect. That is if you check the web, you will notice that the avatar is not updated instantly, you will have to wait a bit.

Steps to reproduce the behavior

I captured a recoding below:

https://user-images.githubusercontent.com/9729923/141289577-032dd375-6475-447b-bfdb-916321164ceb.mp4

Tested on [device], Android [version], WPAndroid [version]

Emulator

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 reviewing the CurrentAvatarSource implementation and PR #15554, then reproduce the avatar update, swipe-off, and relaunch sequence described in the issue. Trace why a second avatar update is not retained after relaunch and verify that repeated updates persist without requiring logout and login.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.