element-hq / element-hq/element-ios

Default app state inaccurate while syncing

Open
#5,343 5 comments 0 reactions 0 assignees View on GitHub
A-Room-List O-Occasional S-Major T-Defect
Dominant language
Swift
Stars
1.8k
Forks
544
PR merge metrics
PR metrics pending

Description

### Steps to reproduce

Sync a large account. Observe the client shows misleading content to the user as if their rooms/account don't exist at all:

| | |
| ---- | ---- |
| ![image](https://user-images.githubusercontent.com/4626865/148187300-dea3651f-8d74-4f7a-b955-7acfe507aa5f.png) | ![image](https://user-images.githubusercontent.com/4626865/148187561-cd33d3a4-163e-4468-842d-2942243c3659.png) |

Reported by @InezMc

### Outcome

We shouldn't display content which misleads the user into thinking all their data may be missing. We should indicate loading consistently as some tabs show a spinner and others don't.

### Your phone model

_No response_

### Operating system version

_No response_

### Application version

_No response_

### Homeserver

_No response_

### Will you send logs?

No

Contributor guide

Open the contributing guide

Research direction

Start by reproducing a large-account sync in the iOS client and compare the tabs that show a spinner with those that display misleading empty content. Trace the default app state and loading indicators used by those tabs. Done means syncing consistently presents loading feedback without implying that rooms or account data are missing.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, swift
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.