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

A failed upload from a file drop or paste leaves a stuck "Loading..." block

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

Mantenedores costumam responder em até 1 dia

@nperez0111 já está trabalhando nisso.

Desde 23/10/2026.

  • #3247 de @nperez0111 — aberto

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Estagnada
Stack de tecnologia
react, typescript
Domínio
frontend, full-stack

Direção de pesquisa

The report identifies handleFileInsertion, editor.uploadFile, and editor.updateBlock, but gives no file path or test name. Start by locating handleFileInsertion and tracing the drop and paste upload flow. Reproduce with uploadFile resolving to an empty string and with a rejected promise; done means a failed upload no longer leaves a Loading block and rejections are handled. An open linked pull request (#3247) already addresses this issue.

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

Descrição

needs-triage
What’s broken?

When uploadFile fails for a file that was dropped or pasted into the editor, the inserted file block keeps showing "Loading..." forever. The user has to delete it by hand.

handleFileInsertion inserts a file block, awaits editor.uploadFile(file, blockId) and then always calls editor.updateBlock(blockId, { props: { url } }).

  • If uploadFile resolves with "" to report a failure, the props don't change, so the block doesn't render again. Its vanilla render replaced the "Add file" button with .bn-file-loading-preview in onUploadStart, and nothing restores it when the upload ends.
  • If uploadFile rejects, the rejection isn't caught. updateBlock never runs, the promise rejection is unhandled, and the block stays on "Loading..." as well.

The file panel's upload tab doesn't show this, because it sets name together with url. The block renders again and offers "Add file".

What did you expect to happen?

A failed upload doesn't leave a stuck placeholder. The block is either removed or goes back to its "Add file" state, and a rejected uploadFile is caught. A documented way for uploadFile to report a failure would help too.

Steps to reproduce
  1. Create an editor whose uploadFile fails: 
    const editor = useCreateBlockNote({
  uploadFile: () => Promise.resolve(""),
});
  2. Drag any file from your computer into the editor, or paste one.
  3. A file block showing "Loading..." stays in the document.

With uploadFile: () => Promise.reject(new Error("rejected")) the block stays as well, and the console shows an unhandled promise rejection.

BlockNote version

@blocknote/core, @blocknote/react, @blocknote/mantine 0.55.0

Environment

No response

Additional context

We work around it by listening to onUploadEnd and, in a timeout after BlockNote's updateBlock, removing the block if it still renders .bn-file-loading-preview.

Contribution
  • I'd be interested in contributing a fix for this issue
Sponsor
  • I'm a sponsor and would appreciate if you could look into this sooner than later 💖
Linguagem predominante
TypeScript
Estrelas
10.3k
Forks
780
Merge médio
3d 6h
PRs com merge (30d)
48

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 TypeCellOS/BlockNote

Todas as issues de TypeCellOS/BlockNote

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.