Mobile Dev browser panel disconnects during an active T3 Code Claude thread

Abierto
#107 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
android, ios, react-native

Línea de trabajo

The payload names no source files, so start by reproducing the disconnect: stop a simulator, then restart it from the docked Mobile Dev panel while a Claude Code thread is open. Find the browser bridge ping/transport and the Claude MCP server lifecycle code, and log which connection drops. Done means the panel stays attached through a restart, or shows a reconnect path that restores the panel and device. Related: #43.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

What happened

During an App Flow retry in T3 Code with the Claude Code plugin, the presenter stopped the selected simulator, then tried to start it again from the docked Mobile Dev browser panel. The panel showed Mobile Dev disconnected from its chat session. Ask the agent to open Mobile Dev again. The T3 thread was still accepting messages. The presenter asked Claude to restart Mobile Dev, and the preview eventually returned.

Expected behavior

Stopping and restarting a simulator should keep the panel attached to its active thread. If the connection fails, show a clear reconnect path that restores the panel and selected device. Capture browser bridge ping/transport results and Claude MCP server lifecycle on repro. The recording does not establish which connection failed. #43 tracks polling after an already-closed Codex thread.

Lenguaje dominante
C++
Estrellas
243
Forks
21
Merge medio
15 h 6 min
PR fusionados (30 d)
57

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de callstackincubator/codex-mobile-dev-plugin

Todos los issues de callstackincubator/codex-mobile-dev-plugin

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.