Skip to content

Neochat gets stuck on Network Error: Pending Retry

Description

If there are unresolved rooms, Neochat stops trying to log in. This doesn't happen in other clients like Element for example.

Steps to reproduce

  1. Have an account with unresolved room
  • This can be a bit difficult to reproduce. I managed to make this happen by having a Conduit server, creating an account there and joining a private space that was made with an account in Matrix.org.
  1. Log in normally with the account
  2. Neochat gets stuck in loop

If need to be I can help testing any fixes for this since I can reproduce the problem every time.

What is the current bug behavior?

Neochat keeps repeating trying to join the broken room link forever, and flashes "Network Error: Pending Retry" but won't log in.

What is the expected correct behavior?

Assuming Neochat would work like other clients, it would ignore joining this room completely, maybe give a warning and then proceed logging in normally.

Relevant logs and/or screenshots

I have changed the actual private space link to "!privateSpaceLink:matrix.org"

quotient.jobs: 200 <- GET https://matrix.akselmo.dev/_matrix/client/r0/capabilities
quotient.jobs.sync: 200 <- GET https://matrix.akselmo.dev/_matrix/client/r0/sync
quotient.main: Unresolved rooms: "!privateSpaceLink:matrix.org"
quotient.main: Incomplete sync response, missing rooms: !privateSpaceLink:matrix.org
quotient.jobs.sync: "SyncJob-1" status IncorrectResponse: 
quotient.jobs.sync: "SyncJob-1": retry #1 in 5 s

Possible fixes

I am not sure if this is libquotinent or Neochat issue.

System/Matrix Information

  • Distribution / Platform: Kubuntu 21.10
  • Qt Version: 5.15.2
  • NeoChat version: used tag v21.12
  • Quotient version: 0.6.6 (i think?)
  • Matrix server: matrix.akselmo.dev
Edited by Akseli Lahtinen