movilba
MOVILBA-135
App auto-refreshes periodically - unintended, fix it
Done high
cmcoder-mba-l-ca
App auto-refreshes every N seconds on dev01 - not designed, desired, or intended. Find the source (polling interval, SWR/router refresh, setInterval, revalidate) and remove it.
Sub-tickets — 1/1 done
MOVILBA-137 Done high
amaudit-mba-l-ca
Activity
-
Root cause isolated: mount-time Server Action reads in stale post-deploy tabs rejected unhandled. Candidate catches every rendered detail-page background action plus session rotation; audit review pending before Dev release.
-
Audit-PASS candidate deployed to Dev v5.4.51 / b3656b49. It catches every rendered mount-time Server Action rejection in vehiculos/[id] plus background session rotation, preventing stale post-deploy action IDs from becoming unhandled page failures. Temporary diagnostics remain until a post-release reproduction/console check confirms the refresh is gone.
-
External evidence gate: child MOVILBA-137 is owned by audit-mba-l-cc and waits for Elazar to reproduce on dev01 /vehiculos/6612 with DevTools Console capture. Required lines: page fetchVehiculo diagnostic (id/userId/permissionsLoading) and useSessionKeepAlive session-update diagnostic. Keep diagnostics live until audit confirms capture; this also blocks the M128 PROD app promotion.
-
M135 audit-PASS stale-action handling and temporary diagnostics promoted in explicitly approved canonical PROD merge df7dd5ef; live health v5.4.54/serviceId 8309. Diagnostics remain pending reproduction evidence; independent production audit requested.
-
PROD deployed-diff audit PASS at df7dd5ef / v5.4.54: stale-action handling and diagnostics are present. Runtime diagnostic reproduction was explicitly not exercised because it requires authenticated DevTools evidence tracked by MOVILBA-137; M135 remains inProgress pending that evidence.
-
MOVILBA-137 root cause confirmed and candidate live DEV b8b87266/v5.4.57: preserve NextAuth session checks but make same user+vehicle primary read idempotent; all temporary refresh diagnostics removed. Awaiting authenticated browser focus trace before final verification/PROD scope.
-
Fresh authenticated runtime trace confirms the unwanted vehicle-detail in-place refetch loop is gone on DEV v5.4.57/b8b87266. No post-load /api/vehiculos or /api/auth/session requests during ~114s, no spinner/reload, diagnostics removed. Static/deployed audit also PASS. Awaiting fresh canonical PROD scope; one harmless connection-handler reinit at ~21s is separate and non-blocking.
-
Runtime-PASS session-focus vehicle refetch fix promoted to PROD in canonical merge 5d73e70a/v5.4.57; live health serviceId 8720, refs agree, typecheck PASS, all temporary diagnostics absent. Independent PROD audit pending.
-
coder-mba-l-ca confirma que no esta activo esta hora; sale de inProgress para no falsear la carga del carril
-
unassigned
-
coder-mba-l-ca
-
Final revalidation: dev HEAD 08123df9 (v5.4.213) contains b8b87266/v5.4.57. The issue was NextAuth focus/visibility recheck, not a periodic timer; the stable userId:vehicleId guard keeps the primary vehicle read idempotent while retaining session security. Prior authenticated DEV trace and independent audit were PASS.
-
Closed after revalidation: existing DEV fix prevents the unintended focus-triggered vehicle-detail refetch; no additional code change is needed.
bug
7w ago by wi-cli-venus
5w ago
2026-09-05 10:06