Horrible UX of updating the Android client downloaded from GitHub

Open
#1,737 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Start at the Android client’s update flow and inspect how it downloads the APK, tracks download completion, and launches installation. Reproduce the dismissed-prompt or app-selection case on Android 8.1; done means the downloaded update remains visible and can be installed without restarting or downloading again.

Written by the indexing model from the issue text.

Description

Needs Looking At

Describe the bug
If your Android client was downloaded from GitHub and there is a new version available, you will not be able to check downloaded update status nor to install the downloaded APK after it was downloaded but you either mistakenly dismissed the installation prompt or have multiple apps that can open APK files, like SAI (Split APK Installer).
Restarting Valour invalidates downloaded file and restarts the download from scratch. Metered networks are in danger.

To Reproduce
Steps to reproduce the behavior:

  1. Run not the latest version of Valour
  2. Click on Update when the modal appears
  3. Wait for download to complete
  4. Wait until your device falls into sleep mode by timeout or dismiss any installation prompt manually

Expected behavior
If the installation was not initialized, Valour puts the 'Update available' or 'Update ready to install' somewhere visible.

System Information:

  • OS: Android
  • Valour Version: 0.9.19
  • Valour Platform: Android 8.1

Additional context
I have Hash Checker by fartem installed alongside with SAI. I don't have default action for .apk files so I'm prompted each time what to do with the file.

Dominant language
C#
Stars
411
Forks
41
Avg merge
5d 4h
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No 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.

More from Valour-Software/Valour

All issues in Valour-Software/Valour

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.