Telegram linking fails with "Cancelled" #71

New issue

Open

opened 2026-11-02 03:58:32 +00:00 by bmt · 1 comment

bmt commented

2026-11-02 03:58:32 +00:00

Member

build: anotherim-js 0.7.20

Linking Telegram ends with "Cancelled." both by QR code and by phone number

steps:

Left click Link Telegram, choose QR code, left click Next, wait a few seconds.
Or choose Phone number, enter the number and the code from Telegram.

expected: The QR code stays until scanned. By phone the account is linked after the code
actual: "Cancelled." in both cases

build: anotherim-js 0.7.20 Linking Telegram ends with "Cancelled." both by QR code and by phone number steps: 1. Left click Link Telegram, choose QR code, left click Next, wait a few seconds. 2. Or choose Phone number, enter the number and the code from Telegram. expected: The QR code stays until scanned. By phone the account is linked after the code actual: "Cancelled." in both cases

bmt added the

bug

telegram_gw

labels

2026-11-02 03:58:32 +00:00

ann referenced this issue from a commit

2026-11-02 04:22:26 +00:00

No registration read of a gateway while a Link sheet is open on it (#71, bmt on 0.7.20, 2026-11-02: "Cancelled." a few seconds into Link Telegram, by QR code and by phone). state/gateways.ts asked the gateway's XEP-0077 registration again on each of its presences, and a get is how a registration starts over: tackygram up to 0.3.15 cancels the login under way with it (#63), and its presence moved as every login started (the engine's new account reporting logged-out) and with each of the user's other devices, so the sheet's own login was cancelled about 0.3 s after it began. Gateways.linking holds the reads for as long as a sheet is open on that gateway and reads once when the last one closes if any was wanted meanwhile; the sheet learns the outcome itself as before. The gateway side is fixed in tackygram fix/issue-71-cancelled (a login is started over only by the client driving it, and the gateway's presence holds still until linked), which fixes every app version on its own. Gate: make check STRICT=1, make test-ui (4584 passed), make test-shell, webkit-smoke on the five service discovery gateway and link screens (59 checks, 0 failed).

ann referenced this issue from a commit

2026-11-02 23:06:19 +00:00

Merge fix/issue-71-link (687a13ae) into rel/0.8: no registration read of a gateway while a Link sheet is open on it (#71).

ann referenced this issue from a commit

2026-11-02 23:06:19 +00:00

0.8.0-beta1, on libtacky v1.2.0-beta2 (2f42a2f2), pairing with tackygram 0.4.0-beta1: rel/0.8 as it stands on c686e6d1 plus the beta2 pin made a beta, as the user scoped it on 2026-11-02 (tags, one Start secret chat for OTR and MTProto PFS, unified dialogs, Media and storage with database encryption that can be turned off, the OMEMO keys window, Fluux polls with their deadline line, the app-wide offline mode removed, the performance pass, the Flatpak drop fix, #71, the 2026-11-02 audit fixes, Tauri 2.12 and Rust 1.99): version 0.8.0-beta1 in the UI package and its lock, tauri.conf.json, Cargo.toml and Cargo.lock, the README's version line and docs/macos.md, and Android versionCode 8000, the semver-derived code as 0.7.5-beta1 had (7005) and above 0.7.21's 7021; the CHANGELOG's Unreleased becomes a compact 0.8.0-beta1 entry ("a beta: anything may happen", short bullets, beta2's album fix among them) with the earlier detailed lines kept under "In detail" for their old and new words; the metainfo's development release 0.8.0~beta1 (appstreamcli validate --no-net passes; online it warns only that https://another.im answers 404 today). Two fixes the release gate found: the WebKit smoke's "padlock tap" and "room encryption info" expected the OMEMO keys window's heading to be exactly "OMEMO keys", while 93cce0e6 (audit U4) names the chat in it when it sits beside the chat, so they now check that it starts so; and Gradle's dependency verification lacked jackson-datatypes-misc-parent-2.15.3.pom, which a fresh Gradle home resolves for tauri-android 2.12.5's jackson-datatype-json-org (sha256 4b2dc9ec, its sha1 7ea4c4da equal to Maven Central's). README's tables measured again: 101,483 lines of code and 106,977 of tests, the UI's 63,865 of 65,202 lines (97.9%, 90.6% of branches), the shell's 9,464 of 9,869 (95.9%; the web image has no llvm-profdata on PATH since the emsdk image, so it ran with emsdk's LLVM tools), the Kotlin's 3,483 of 3,630 (96.0%), the worker's 872 of 872. Gates on this tree: make check STRICT=1 clean (2,319 strings; "Unmute" obsolete in the four catalogues); make test-ui 4,822 passed, 8 skipped (415 files); make test-shell 303 in 37; make test-worker green (the wasm backend rebuilt from beta2); the Android JVM unit tests free 509 and gms 512 passed (on the beta1 tree; the Kotlin and its build do not see libtacky's Tcl); make release-check passed; the WebKit smoke 852 screens, 8,773 checks, 0 failed with SMOKE_JOBS=16.

ann commented

2026-11-04 18:54:56 +00:00

Owner

Two things ended the login: the gateway cancelled a QR or phone login whenever any other client of the same account asked it for the registration form, and its own "Not logged in" presence at the start made the app read the link as cancelled about a third of a second later. Both are fixed: tackygram 0.4.0-beta1 and later (current 0.4.0-rc2) keep the login until it finishes or you cancel it, and the app since 0.8.0-beta1 no longer takes that presence for a cancel. telegram.another.im runs the fixed gateway.