adding an account doesn’t switch to it #22

New issue

Closed

opened 2026-10-17 20:11:29 +00:00 by bmt · 1 comment

bmt commented

2026-10-17 20:11:29 +00:00

Member

build: anotherim-js 0.6.0 (Windows)

After adding a second account, the app stays on the previous and the new account has to be picked in the account menu.

steps:

Sign in to an account
Account menu → "Add an account" → sign in to another account

expected: the new account opens right after sign-in

actual: the previous account stays open

build: anotherim-js 0.6.0 (Windows) After adding a second account, the app stays on the previous and the new account has to be picked in the account menu. steps: 1. Sign in to an account 2. Account menu → "Add an account" → sign in to another account expected: the new account opens right after sign-in actual: the previous account stays open

bmt added the

bug

windows

ui/ux

labels

2026-10-17 20:19:00 +00:00

ann referenced this issue from a commit

2026-10-18 10:26:07 +00:00

An account added from the account menu opens as soon as it is signed in (#22, 0.6.0 on Windows: "adding an account doesn't switch to it"): the add-account sheet closed on the card's signed-in and nothing put the new account in front, so the app stayed on the account the reader was on and the new one had to be picked from the menu. The shell's signed-in listener, which every card's sign-in reaches (the password, the provider's own page through OAuth, a sign-up, on the welcome screen and in the sheet alike), now calls selectAccount with the account that connected, which also closes the old account's open chat as a pick from the menu does; a refused or abandoned sign-in never says signed-in, so the front stays where it was. A broker sign-in leaves the sheet when the browser opens, so sso-signin.ts watches that account itself and brings it to the front on its first connect, dropping the watch on a conn AuthError. welcome-shell.test.ts adds an account from the sheet and finds it in front, and has a refused one leave the front and the open chat alone; one-client.test.ts adds one through the mock broker and finds it in front. The changelog's Unreleased section names it.

ann commented

2026-10-18 10:35:23 +00:00

Owner

The add-account sheet closed itself on sign-in but never selected the new account, so the old one stayed in front. A successful sign-in from the sheet now puts the new account in front: password, provider page, sign-up and organisation sign-in. A refused or cancelled sign-in leaves the current account as it was.

Fixed in 0.6.1: https://dev.another.im/another-im/anotherim-js/releases/tag/v0.6.1

ann closed this issue

2026-10-18 10:35:23 +00:00