Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Mosaic reconnect loses its error when OAuth navigation fails

Aberta
  • Algo errado?
#10,118 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
react, typescript
Domínio
authentication, frontend

Direção de pesquisa

Start by reading the connected-account reconnect flow in projectConnectedAccounts, usePendingAction, and the controller mapping mentioned in the issue; inspect the existing tests near PR #10086 for the relevant setup. Add regression coverage for error transfer across account recreation and reauthorization, redirect hold, and retry behavior. Done when both reproduced navigation-failure paths show the error and retry remains available.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Connected-account reconnect loses its error when navigation fails.

Reproduced both paths in Chromium against the latest-main-rebased PR #10086 branch.

  1. Seed a disconnected Google external account with an unverified google_one_tap verification and external_account_missing_refresh_token, then click Manage Google and Reconnect.
  2. Alternatively, seed a verified Google account and render the section with additionalOAuthScopes={{ google: ['calendar'] }}, then click Manage Google and Reconnect.
  3. Make clerk.navigate reject with Error("Navigation failed").

Expected the row or replacement Connect action to show "Something went wrong. Please try again." Both paths permit another connection but render no error. An unconditional findByText assertion fails for both cases. Connect does show the error.

The successful Frontend API response makes the account unverified without a verification error. projectConnectedAccounts hides such accounts and offers a Connect action instead. usePendingAction records the failure under the original account ID. The controller maps reconnectError to account rows with that ID, but the row has disappeared. Recreation also replaces the account with a new ID.

Keep this source fix separate from PR #10086, which only restructures tests. Cover error transfer across account recreation and reauthorization, redirect hold, and retry behavior with regression tests.

Linguagem predominante
TypeScript
Estrelas
1.8k
Forks
477
Merge médio
1d 18h
PRs com merge (30d)
287

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de clerk/javascript

Todas as issues de clerk/javascript

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.