[Windows] App Shot attach fails before capture starts, then recovers after a multiline draft

Aperta
  • Qualcosa non va?
#52,344 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript
Ambito
desktop-dev, frontend

Direzione di ricerca

The report points at the renderer bundle webview/assets/app-initial-25361a10f2bf.js: the capture function a5s checks the attachment animation destination before it logs request creation, and the callback in Mxc returns null when attachmentsContainerRef.current is missing. Start by confirming whether that container is absent in the single-line layout, and see where the early return happens without a lifecycle log. Done means the early return is logged with its reason and an empty message box either attaches or shows a useful error. The intermittent recovery is unexplained, so reproduce it before changing anything.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

app bug windows-os
What version of the Codex App are you using (From About Codex dialog)?

Windows package OpenAI.Codex, version 26.1002.7124.0, collected with Get-AppxPackage. The About dialog was not inspected.

What subscription do you have?

Not provided. This report concerns desktop App Shot capture and composer state.

What platform is your computer?

Microsoft Windows 11 Enterprise 25H2, build 26200.9550, x64.

What issue are you seeing?

App Shot repeatedly showed "Unable to attach app shot" after a PC reboot, using either the configured DoubleShift shortcut or the message box's + -> Attach [app] menu. Bringing Codex fully into view and retrying from an existing chat did not resolve it.

For the failing shortcut attempts, the desktop log showed target discovery and "Appshot shortcut started appshot", but no "Appshot capture request created", start-request, or completion records. The menu retries also produced no capture lifecycle records. The native helper and pipe had initialized successfully.

After entering a two-line draft (test, Shift+Enter, test) and retrying, capture and attachment succeeded. The screenshot and accessibility text arrived in the chat. Importantly, subsequent captures also worked with an empty message box, according to the user. This is an intermittent or state-dependent failure; an empty message box alone is not a reliable reproduction condition, and the two-line draft may have unblocked or initialized composer state.

What steps can reproduce the bug?

Observed sequence on 9 October 2026, GMT+8:

  1. Start Codex after rebooting Windows, and open a new or existing chat with an empty message box.
  2. Bring Google Chrome to the foreground and trigger App Shot with DoubleShift. Repeated attempts failed with the generic attachment error.
  3. Bring Codex fully into view and try + -> Attach [app] from an existing chat. The same error appeared.
  4. Enter a two-line draft without sending it, then trigger App Shot again. This attempt succeeded.
  5. Later, retry with an empty message box. The user reported success, and further capture successes were present in the log.

This is an observed recovery sequence, not a deterministic minimal reproduction. The exact state that originally caused the failure remains unknown.

What is the expected behavior?

App Shot should attach from an empty message box. If composer destination geometry is unavailable, capture should recover or provide a useful error and log the reason instead of silently returning before the request lifecycle begins.

Additional information

The failing shortcut attempts were at approximately 08:49 GMT+8. The first verified successful capture was at 08:57, completing in 1,448 ms with status=success, hadScreenshot=true, and hadAxText=true. Two further captures completed at approximately 09:08 in 1,024 ms and 1,058 ms. No application/runtime files or configuration were modified between the failed post-reboot attempts and these successes.

Possible frontend cause, not confirmed by live DOM inspection: in the installed renderer bundle webview/assets/app-initial-25361a10f2bf.js, capture function a5s validates the attachment animation destination before logging request creation or adding pending capture state. The callback in Mxc returns null if attachmentsContainerRef.current is absent. The normal single-line layout can omit the attachment container. A null destination triggers the generic attachment toast and returns without a capture lifecycle log. The outer shortcut can nevertheless log "started appshot" because it invokes that async function without awaiting it. This is consistent with the observed logs, but does not establish why the state later recovered and empty drafts started working.

Useful diagnostic additions would include whether the attachment container exists, the layout mode, UI scale, destination validation result, and the trigger source when this early return occurs.

The user also reports that Codex's window resizes every time App Shot is used, even when capture succeeds. This appears related to the existing window-state report #50476. The exact before/after bounds and maximized state have not been independently measured.

Related reports: #26051 (intermittent per-chat attachment failure on macOS) and #50476 (Windows App Shot window restoration/resizing). This report adds Windows pre-request failure evidence and the observed multiline recovery sequence.

Earlier, before the reboot, a separate native load_appshot_capture_source timeout was logged. That timeout did not recur in the successful post-reboot captures, and has not been established as the cause of the pre-request failures described here.

No private screenshots, browsing contents, full session transcripts, account details, or local user paths are included.

Lingua principale
Rust
Stelle
131k
Fork
20.7k
Merge medio
1m
PR unite (30g)
997

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openai/codex

Tutte le issue di openai/codex

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.