v3.8.42: swipe actions, connect states, auth race, badge colors

[taylorcox75]

Release v3.8.42. package.json bumped to match CHANGELOG[0].

⚠️ easBuild: true — merging this to main builds and submits to the App Store.

Fixes

Swipe actions — The action panel is absoluteFill over the whole row while the card inside carries a 4px vertical margin and a 12/16px radius, so the orange/red backgrounds stood proud of the card with square corners. Separately, the icon scale interpolations were calibrated for a reveal animation Swipeable doesn't perform (the panel is static; the card slides over it), so icons flashed or showed blank blocks. Actions now slide in with progress — the library's own pattern — and the panel is clipped to the card's bounds.

"Authentication failed" when switching servers — The previous server's 2s /sync/maindata poll stayed enabled through a connect. apiClient.setServer(newServer) clears the cookie, the poll tick then 403s, and the shared 403 handler wiped the new server's just-issued session cookie — so the connect's own getVersion() failed with an auth error. Retrying worked because the poll was disabled by then. Three-part fix:

• apiClient stamps each request with a session epoch and only lets a 403 clear the cookie when the request was issued under the current session; a superseded 403 throws a distinct non-reconnectable error.
• The connect mutation drops connection state in onMutate, stopping the poll before login runs.
• reconnect/checkAndReconnect no-op while a connect is in flight, the in-flight promise is keyed by server id, and ServerManager.reconnect() takes an explicit server (storage's "current server" isn't written until after login, so it can still name the previous one mid-switch).

"No Torrents" during a connect — initialLoadComplete is set once and never reset, so after any earlier session the skeleton condition was false during a connect and the screen fell through to the empty-list branch for the full 10s timeout. New isConnecting flag on ServerContext gates the skeleton.

Unreadable Connect button — colors.error is an rgba() string, and colors.error + '18' appends hex alpha that RN's unanchored color parser silently ignores, producing an opaque fill — error-red text on error-red. New withAlpha() util (hex/rgb/rgba, with tests) fixes the pill and the four server debug-row sites with the same latent bug.

Server badge color changing on its own — The fallback was avatarColor(name), rehashing an 8-colour palette on every keystroke and shifting again on rename. Servers now use a fixed DEFAULT_AVATAR_COLOR until the user picks one. avatarColor stays for category/tag colours.

Color picker — Added a Save button beside the X. Cosmetic only; selections already apply live.

Sound effects removed — Native module, utils/sounds.ts, call sites, preference fields, settings UI and all six locales' strings.

Existing users

• No preference key was renamed or repurposed. The two sound keys are simply no longer read; savePreferences spreads the stored object so they stay untouched in AsyncStorage and every other preference is preserved.
• No stored ServerConfig field changed. Servers that never had an explicit iconColor will render with the default blue instead of a name-derived colour — a deliberate visual change, no data touched, and any colour can still be picked.
• No colors theme keys renamed; withAlpha only changes how alpha is applied at render time.
• 4.x compatibility untouched — no API endpoints or parameters changed.

Test plan

• npx tsc --noEmit — clean
• npm test — 76 suites / 1089 tests passing (includes new tests/utils/color.test.ts and session-epoch cases in tests/services/client.test.ts)
• npm run lint — 0 errors (38 baseline warnings)
• npm run format

Swipe rendering, the connect/skeleton states and the badge default need an on-device pass — they can't be verified from tests.

🤖 Generated with Claude Code