keybase / keybase/client

Android: refresh files pages on demand or more frequently

Open
#18,276 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

What I did

I went to a shared private folder after a team member messaged me to say they had put a new files there.

What happened

The folder showed that it was empty, even after waiting a long time. I tried exiting to another screen and returning and still it didn't show. I tried closing and reopening the app and still it didn't show. I uploaded a file to the folder and 💥 the file uploaded by my team mate also appeared as if my uploading a file triggered refreshing.

What I expected to happen

To either see the file appear in a timely manner or there be someway for me to refresh the folder I'm viewing.

Why did I expect this

It's very unclear how old the data is I'm viewing on file and git views and without an ability to refresh a user can be stuck viewing old files which hampers collaboration.

Contributor guide

No contributing guide indexed for this repository

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 reproducing the issue in an Android shared private folder: observe whether a teammate's newly added file appears without another file operation, and check the current files-page refresh behavior. Done means users can see new files in a timely manner or manually refresh the folder view.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.