[Android Remote][Realtime Voice] Image-generation section remains stuck loading while Windows host thread opens normally

Summary

A Codex thread created from realtime Voice can be opened normally on the Windows Codex Desktop host, but ChatGPT Android Remote leaves the image-generation section of that same thread stuck on loading placeholders indefinitely.

This appears separate from a local thread-history projection problem that affected the same environment. That projection problem was repaired locally, restoring recent conversation history, but the Android image-generation section still does not hydrate.

Environment

• Host: Windows Codex Desktop
• Remote client: official ChatGPT Android app
• Same ChatGPT account / connected Remote host
• Thread creation path: realtime Voice
• The exact current Desktop/mobile build numbers were not captured for this report

Reproduction

1. From ChatGPT Android Remote, start a new Codex thread using realtime Voice.
2. Very early in the thread, invoke image generation.
3. Allow the image-generation turn to complete on the host.
4. Open the same thread on the Windows Codex Desktop host.
5. Confirm the Project/thread itself opens normally on Desktop and the conversation history is available.
6. Open the same thread from Android Remote.
7. Observe that the image-generation section remains indefinitely in a loading/skeleton state instead of rendering normally.

Important control

The Windows host can open the Project and the same chat/thread normally.

A separate local paginated-history projection failure was also diagnosed in this environment (expected ordinal 1337, got 1336 caused by a duplicated rollout ordinal). That projection issue was repaired by advancing only the derived history projection cursor past the verified duplicate metadata record; the canonical rollout was not modified.

After that repair:

• recent conversation history became visible again;
• the thread remained healthy on Windows Desktop;
• the Android Remote image-generation section still remained stuck loading.

This suggests the remaining failure is not caused by the previously stalled local thread-history projection.

Expected behavior

Android Remote should hydrate and display the image-generation item/section for a thread that is valid and usable on the connected Windows host.

If the image/tool item cannot be hydrated, Remote should surface an explicit bounded error rather than leaving a permanent loading placeholder.

Actual behavior

The thread itself is reachable, but the image-generation section never finishes loading on Android Remote while the same Project/thread is usable on Windows.

Suspected area

This looks like a Remote item/tool-output hydration or attachment/artifact projection problem specific to realtime-Voice-created threads, rather than canonical transcript loss.

Potentially relevant neighboring reports include Android Remote thread hydration/loading failures such as #39931 and #38023, but this report isolates a completed image-generation section inside a realtime-Voice-created thread.

Related separate issue

The same Windows/Android environment also has Project inventory synchronization problems: Projects/threads that are healthy on Windows do not reliably appear in Android Remote. That is tracked separately in #41470 / #41197.

Privacy

No project names, thread IDs, local paths, prompt contents, generated images, account identifiers, or raw logs are included here. Screenshots can be provided separately if needed.

No source files or tests are named. Start by reproducing the realtime Voice flow and comparing the completed image-generation item on Windows Desktop with Android Remote, using the related hydration reports as context. Done means the Android section renders for the valid thread, or shows a bounded error instead of an indefinite loading placeholder.