nvrl/proton-drive-linux
1
0 Fork 0
mirror of https://github.com/narrrl/proton-drive-linux.git synced 2026-11-03 16:41:26 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix(core,gui,cli): a blocked sign-in no longer asks to update the app (B209)

Browse Source 
Proton answers a sign-in it blocks for abuse or rate limits with code
2028 and the text "This version of the app is no longer supported". The
SDK read 2028 as Unknown, so the app passed that text through and told
users to update a current release (issues #28, #39).

- deps: proton-sdk and proton-drive-rs 0.8.3, which name 2028 Blocked
- core: error::sign_in_blocked detects it
- gui: the login page says Proton is refusing sign-in for now and that
  waiting helps, translated in every catalog
- cli: pdfs login adds the same hint to the error
- cli: pdfs diagnose warns instead of failing when cache.db does not
  exist yet; the daemon creates it after the first sign-in
- docs: BUGS.md B209, changelog, troubleshooting entry
This commit is contained in:
nvrl committed 2026-10-13 20:29:23 +02:00
1 parent 2633b4ed72
commit 478a0e6cdd
17 files changed
+481 -310
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/BUGS.md
+28
View File
@@ -100,6 +100,7 @@ a live account since.
| Entry | Title |
|---|---|
| [B209](#b209--a-blocked-sign-in-says-the-app-version-is-no-longer-supported) | A blocked sign-in says the app version is no longer supported |
| [B208](#b208--a-file-landing-while-its-folder-is-pinned-is-kept-but-not-available-offline) | A file landing while its folder is pinned is kept but not available offline |
| [B207](#b207--a-move-between-locations-goes-ahead-under-a-file-opened-just-after-its-create-landed) | A move between locations goes ahead under a file opened just after its create landed |
| [B206](#b206--an-upgrade-leaves-the-old-daemon-running-and-nothing-says-so) | An upgrade leaves the old daemon running, and nothing says so |
@@ -311,6 +312,33 @@ a live account since.
Newest first.
### B209 — A blocked sign-in says the app version is no longer supported
**Status:** Fixed, not verified live
**Found:** 2026-10-13, issue #39: the first sign-in on a fresh 3.4.0 install showed "This version
of the app is no longer supported. Please update to continue using the app." Issue #28 showed the
same text on 3.0.0 to 3.1.2, and its debug log gave `path="/auth/v4" http_status=422 code=2028`.
Sign-in worked there after a day without attempts, with no change to the client.
**Where:** `login_error_message` in `crates/pdfs-gui/src/app/pages/login.rs`; `cmd_login` and
`cmd_diagnose` in `crates/pdfs-cli/src/main.rs`
**Repro:** Needs Proton to block the account or network, which cannot be triggered on purpose.
**Cause.** Proton answers a sign-in it blocks for abuse or rate limits with code 2028. Its `Error`
text claims the version is no longer supported. The SDK had no name for 2028, so it read as
`Unknown`, and the app passed Proton's text through. Users were told to update a current release.
`pdfs diagnose` also failed the `database` check on a fresh install, before the daemon had ever
started, which looked like part of the fault.
**Fix.** proton-sdk 0.8.3 names 2028 `ResponseCode::Blocked`. `error::sign_in_blocked` detects it,
and the app and `pdfs login` say that Proton is refusing sign-in for now and that waiting helps.
`pdfs diagnose` warns instead of failing when `cache.db` does not exist yet.
**Test:** `error::tests::only_code_2028_is_a_blocked_sign_in`,
`pages::login::tests::a_blocked_sign_in_does_not_ask_for_an_update`.
---
### B208 — A file landing while its folder is pinned is kept but not available offline
**Status:** Fixed, not verified live