Slow networks break invite codes #202

New Issue

2026-04-14T23:29:34Z

hodlbod commented

2026-04-14 23:29:34 +00:00

If you throttle your connection, the create invite link times out without getting a code back.

hodlbod added this to the Current milestone 2026-04-14 23:29:34 +00:00

hodlbod added the dev label 2026-04-14 23:29:34 +00:00

priyanshu_bharti commented

2026-04-14 23:41:05 +00:00

Please assign this

priyanshu_bharti was assigned by hodlbod

2026-04-14 23:58:22 +00:00

DeveshSingh commented

2026-04-15 12:57:20 +00:00

Hi @hodlbod , I looked into the issue and found that the issue stems from an unhandled timeout error stopping the execution.

In SpaceInvite.svelte, the 3-second network request for the invite claim times out on slow networks. Because the Promise. All calls aren't wrapped in a try/catch block; the exception skips the loading = false step entirely, which traps the user in an infinite loading spinner.

To fix this, we can :
-Wrap the request in a try/catch block to handle the timeout gracefully.
-Slightly increase the timeout limit (e.g., to 7 or 10 seconds) to be kinder to slow connections.
-Ensure loading = false executes regardless of success or failure (e.g., using a finally block). This allows the UI to correctly fall back to providing a claimless invite link instead of entirely freezing.

Is this approach looking good to you? If yes, then I can move forward.

Hi @hodlbod , I looked into the issue and found that the issue stems from an unhandled timeout error stopping the execution. In SpaceInvite.svelte, the 3-second network request for the invite claim times out on slow networks. Because the Promise. All calls aren't wrapped in a try/catch block; the exception skips the loading = false step entirely, which traps the user in an infinite loading spinner. To fix this, we can : -Wrap the request in a try/catch block to handle the timeout gracefully. -Slightly increase the timeout limit (e.g., to 7 or 10 seconds) to be kinder to slow connections. -Ensure loading = false executes regardless of success or failure (e.g., using a finally block). This allows the UI to correctly fall back to providing a claimless invite link instead of entirely freezing. Is this approach looking good to you? If yes, then I can move forward.

priyanshu_bharti commented

2026-04-15 13:50:30 +00:00

hii @DeveshSingh
I’ve already tested this issue (and a few other similar slow network / timeout related bugs). Everything matches what you described.
I’ll raise a PR for this very soon

hii @DeveshSingh I’ve already tested this issue (and a few other similar slow network / timeout related bugs). Everything matches what you described. I’ll raise a PR for this very soon

priyanshu_bharti referenced a pull request that will close this issue

2026-04-15 17:11:13 +00:00

Fix #202 slow-network invite timeout handling #207

priyanshu_bharti referenced this issue

2026-04-15 17:18:07 +00:00

Fix #202 slow-network invite timeout handling #207

hodlbod closed this issue

2026-04-15 22:01:01 +00:00

hodlbod referenced this issue from a commit

2026-04-15 22:01:03 +00:00

Fix #202 slow-network invite timeout handling (#207)

Sign in to join this conversation.