Cannot add comments remotely: "Response body object should not be disturbed or locked"

[labob246]

When connecting to TaskTrove from my network, I can add comments and subtasks to any task. However, when I access remotely via my subdomain, I can do everything including subtasks, BUT I cannot add any comments. I get the error: Failed to updated task: Failed API request: 500

[dohsimpson]

that's strange, could you check the server log when the 500 errors happened and share it here?

[labob246]

HI. I'm not too good at finding logs and everything and so i'm not to sure where you want me to check. I run this in a docker through a tunnel for remote access. It's only then i get the error and only on adding comments. I checked the TaskTrove docker log and there is nothing in there about the error. I tried a different browser and no luck there either. Whether I use my mobile device or desktop on my lan, only when i use the domain access does it do this. I was curious if he had happened anywhere else, and it's not too big of a deal for me right now. I know you are working on the phone apps so that will probably be my remote connection. BTW, as an old guy, I've seen and used a lot of apps and I genuinely think yours is great. Been looking for a task app for ages and the fact this self-hosts is huge for me. Thank you for it all.

[dohsimpson]

Thanks for the kind words. I haven't been seeing this issue so far. Nor have anyone reported this yet. By server log, I do mean the docker log. Please keep this issue posted if you have new findings.

[labob246]

I tried to add a comment this evening and immediately went to the Tasktrove logs and found this:
⨯ TypeError: Response body object should not be disturbed or locked
at new i (.next/server/chunks/6755.js:12:77134)
at l.fromNodeNextRequest (.next/server/chunks/6755.js:22:9709)
at X (.next/server/app/api/v1/tasks/route.js:1:12690)

[dohsimpson]

That's very helpful! This is the same issue from #153. It is due to a bug in NextJS. I've been following their thread and it seems that they have patched this in NextJS16. I've been thinking of upgrading but it will take some effort.

Let's keep this issue open to track this.