Plex pin flow reports connected but strands authorized accounts with no servers #345
Closed
opened 2026-07-13 22:48:23 +02:00 by timothy
·
2 comments
No Branch/Tag Specified
main
renovate/dotnet-monorepo
renovate/meziantou.analyzer-3.x
renovate/lucene.net
renovate/sqlitepclraw.bundle_e_sqlite3-3.x
renovate/cliwrap-3.x
913-scripted-playout-401
release/v26.15.0-notes
issue-806-guard-populations
scratch/767b-poisoned
scratch/767b-control
release/v26.14.0-notes
release/v26.14.0
docs/510-skill-logo-bug-policy
fix/510-watermark-resolution-policy
fix/629-verdict-classifier-falseopens
fix/609-decisions-edit-token-scope
issue-135-clear-to-none
release/v26.12.0-notes
fix/409b-lastscan-api-parity
fix/401-updatechannel-mirror-422
fix/327-playlist-rename-validation
fix/410-scancancel-log-level
fix/409-447-librariesscreen-neverscanned
fix/338-zap-exit-code
fix/367-plex-budget-message
fix/310-debom-legacy-cs
ci/604-lane-rebalance
feat/388-design-mirror
feat/247-test-ownership
feat/247-primary-action
feat/357-player-owned-playback
feat/357-jellyfin-plugin-poc
fix/289-mcp-hardening
issue58-mcp
feat/244-channels-extract
ci/auto-bump-prod-compose
feat/multi-rerun-collections-api
feat/collections-api
feat/quick-wins
feat/185-docs-part2
feat/140-collections-screen
feat/146-channel-edit
feat/147-classic-ui-link
issue22-renovate-dashboard
feat/91-cutover
feat/63-composite-create
feat/65-library-browse
feat/85-epg
feat/86-schedule-editor
feat/109-dashboard-data
feat/99-session-tracking
fix/dockerfile-node-tag
feat/59-spa-foundation
docs/59-ui-redesign-brief
feat/102-json-guide
feat/111-schedule-durations
feat/104-artwork-upload
feat/103-media-sources-api
feat/playouts-read-api
feat/108-health-api
feat/105-picker-list-endpoints
issue-97-channel-state-api
issue42-jellyfin-musicvideos
issue46-rest-api-error-contract
dependabot/nuget/ErsatzTV.FFmpeg.Tests/multi-d307a2e06f
qsv-improvements
hdr-vulkan-cuda-test
v26.16.0
v26.15.0
v26.14.0
v26.13.0
v26.12.0
v26.11.0
v26.10.0
v26.9.0
v26.8.0
v26.7.0
blazor-final
v26.6.0
v26.5.0
v26.4.0
v26.3.1
v26.3.0
v26.2.0
v26.1.1
v26.1.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.0
v25.1.0
v0.8.8-beta
v0.8.7-beta
v0.8.6-beta
v0.8.5-beta
v0.8.4-beta
v0.8.3-beta
v0.8.2-beta
v0.8.1-beta
v0.8.0-beta
v0.7.9-beta
v0.7.8-beta
v0.7.7-beta
v0.7.6-beta
v0.7.5-beta
v0.7.4-beta
v0.7.3-beta
v0.7.2-beta
v0.7.1-beta
v0.7.0-beta
v0.6.9-beta
v0.6.8-beta
v0.6.7-beta
v0.6.6-beta
v0.6.5-beta
v0.6.4-beta
v0.6.3-beta
v0.6.2-beta
v0.6.1-beta
v0.6.0-beta
v0.5.8-beta
v0.5.7-beta
v0.5.6-beta
v0.5.5-beta
v0.5.4-beta
v0.5.3-beta
v0.5.2-beta
v0.5.1-beta
v0.5.0-beta
v0.4.5-alpha
v0.4.4-alpha
v0.4.3-alpha
v0.4.2-alpha
v0.4.1-alpha
v0.4.0-alpha
v0.3.8-alpha
v0.3.7-alpha
develop
v0.3.6-alpha
v0.3.5-alpha
v0.3.4-alpha
v0.3.3-alpha
v0.3.2-alpha
v0.3.1-alpha
v0.3.0-alpha
v0.2.5-alpha
v0.2.4-alpha
v0.2.3-alpha
v0.2.2-alpha
v0.2.1-alpha
v0.2.0-alpha
v0.1.5-alpha
v0.1.4-alpha
v0.1.3-alpha
v0.1.2-alpha
v0.1.1-alpha
v0.1.0-alpha
v0.0.62-alpha
v0.0.61-alpha
v0.0.60-alpha
v0.0.59-alpha
v0.0.58-alpha
v0.0.57-alpha
v0.0.56-alpha
v0.0.55-alpha
v0.0.54-alpha
v0.0.53-alpha
v0.0.52-alpha
v0.0.51-alpha
v0.0.50-alpha
v0.0.49-prealpha
v0.0.48-prealpha
v0.0.47-prealpha
v0.0.46-prealpha
v0.0.45-prealpha
v0.0.44-prealpha
v0.0.43-prealpha
v0.0.42-prealpha
v0.0.41-prealpha
v0.0.40-prealpha
v0.0.39-prealpha
v0.0.38-prealpha
v0.0.37-prealpha
v0.0.36-prealpha
v0.0.35-prealpha
v0.0.34-prealpha
v0.0.33-prealpha
v0.0.32-prealpha
v0.0.31-prealpha
v0.0.30-prealpha
v0.0.29-prealpha
v0.0.28-prealpha
v0.0.27-prealpha
v0.0.26-prealpha
v0.0.25-prealpha
v0.0.24-prealpha
v0.0.23-prealpha
v0.0.22-prealpha
v0.0.21-prealpha
v0.0.20-prealpha
v0.0.19-prealpha
v0.0.18-prealpha
v0.0.17-prealpha
v0.0.16-prealpha
v0.0.15-prealpha
v0.0.14-prealpha
v0.0.13-prealpha
v0.0.12-prealpha
v0.0.11-prealpha
v0.0.10-prealpha
v0.0.9-prealpha
v0.0.8-prealpha
v0.0.7-prealpha
v0.0.6-prealpha
v0.0.5-prealpha
v0.0.4-prealpha
v0.0.3-prealpha
v0.0.2-prealpha
v0.0.1-prealpha
Labels
Clear labels
ad-hoc
api
bug
ci-cd
content
dependencies
enhancement
frontend
in-progress
jellyfin
parked
priority: high
priority: low
priority: medium
review
security
One-off / ad-hoc work not tracked by a dedicated issue
REST API / HTTP endpoints
Something isn't working
Build, test, deploy pipeline
Channel content / schedules / playlists
Dependency updates (Renovate)
New feature or improvement
ChicoryTV React SPA frontend
Claimed by an active session — do not pick up
Jellyfin tuner / IPTV integration
Excluded from automatic queue pickup; work only when explicitly selected
Adversarial review finding
Security / vulnerability fix
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: timothy/ersatztv#345
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
A real Plex pin-flow run for #333 reached the valid API state
isAuthorized: true,isLocked: false,servers: []. The SPA then displayed mutually contradictory state:No matching open or closed issue was found with searches for “Plex sign out”, “Connected to Plex”, and “Plex servers”.
Reproduction
/app/libraries/plex.GET /api/v1/media-sources/plexreturns authorized/unlocked with an empty server list.This was reproduced against the disposable
ersatztv-testdeployment on 2026-07-13. Server logs showed successful authentication and no server-discovery exception. Cleanup requiredPOST /api/v1/media-sources/plex/sign-outoutside the SPA; afterward the API and SPA both returned to a clean signed-out state.Root cause evidence
web/src/mediaSources/pinFlowPoll.tstreats unlocked + authorized as terminal success and always emits “Connected to Plex.”web/src/screens/PlexSourceScreen.tsxdefinesconnectedsolely asservers.length > 0.Expected
The authorized-zero-server state is coherent and recoverable: it must not claim a server connection, it should explain that the Plex account is authorized but no eligible servers were discovered, and it must offer sign-out.
Done-when
serversis empty.ersatztv-test, 2026-07-13) is the validation evidence. A fresh live repro requires a Plex account with zero eligible servers, which can't be synthesized on demand; the state transition + sign-out are covered deterministically by the new regression tests (finalizing/terminal/budget-exhausted cells + sign-out from the empty state).adversarial review passed — two cold-context passes; the initial diff BLOCKED on a real High (locked-state contradiction), fix re-review MERGEABLE @
6532929c.Claiming (Claude Code / Opus 4.8 orchestrator session).
Context: arc tracker #237 is closed and no open frontier/milestone/
reviewitems remain, so this is a backlog pickup. #345 is the highest-priority unclaimed available issue (the otherpriority: high, #357, is being worked under PR #358 + active worktrees). Working it as a self-contained SPA fix off the localized root cause in the body (pinFlowPoll.ts+PlexSourceScreen.tsx).Plan: distinguish account-authorization from server-discovery in the pin-flow terminal state; make sign-out available for the authorized/unlocked/empty-servers state; align the Connection card + actions with authorization state; add regression tests for the authorized/unlocked/empty transition and sign-out; run SPA quality gates. Will verify against the localized code before treating the body's root-cause as ground truth.
Closed — fixed in PR #366 (merged to
main@ee044ab2)What was done
Separated Plex authorization (a stored token,
isAuthorized) from connection (discovered servers,servers.length > 0) in the SPA. The authorized/unlocked/empty-servers state is now coherent and recoverable: it no longer claims "Connected to Plex.", it explains that the account is authorized but no eligible servers were discovered, and it offers Sign out.Root cause
PlexSourceScreenderived every affordance (subtitle, Sign-in visibility, Sign-out visibility, Servers card) fromconnected = serverList.length > 0, andevaluatePinFlowreturnedsuccess("Connected to Plex.") for any released-lock + authorized observation regardless of server count. SoisAuthorized:true, isLocked:false, servers:[]producedconnected=false→ "Not signed in." + Sign in shown + Sign out hidden, while the pin-flow status simultaneously claimed a connection — leaving the stored authorization unremovable via the UI.Fix (pure SPA — no API change; the sign-out endpoint already works with empty servers)
web/src/mediaSources/pinFlowPoll.ts: newauthorized-no-serversterminal status + ahasServersobservation field; the released-lock branch yieldssuccessonly when a server was discovered, else the honest empty-servers terminal.web/src/screens/PlexSourceScreen.tsx:hasPlexAccount = isAuthorized || hasServersgates Sign in vs Sign out; a four-way Connection subtitle; an explanatory summary; the Servers card stays gated on real servers. The empty-servers presentation is gated on!isLockedso it never fires during the in-flightfinalizing/budget-exhaustedwindows (caught in review — see below).PlexSourceScreen.test.tsx(pin-flow terminal, finalizing/budget-exhausted guards, fresh-reload sign-out) +pinFlowPoll.test.ts(new machine case).Files changed: the 4 files above (+29/−1 in the review fix commit).
Review: two cold-context adversarial passes. The initial diff was BLOCKED on a real High — the empty-servers messaging ignored
isLockedand would render during discovery, even urging a sign-out mid-sync; fixed and re-reviewed MERGEABLE @6532929c. Both regression guards were negative-control-proven.Verification:
npm test780/780,npm run lintclean,npm run buildclean; CI green on the PR head.Deferred / follow-up: filed #367 (
priority: low) for a pre-existing, orthogonal gap the review surfaced — thebudget-exhaustedmessage says "Use Refresh to check again," but there's no global Refresh control when zero servers exist.Docs: no doc update required — no route added/redirected, no
/api/*endpoint change, no SPA convention changed, no decision reversed (per the docs-update table).