A further update following some iOS PWA problems on 28 October 2026, now on iOS 27.2 (iPhone 16 Pro).
These were not exact reproductions of the original lost-dictation problem, but I have checked the Caddy and nginx logs to understand what happened.
10:58 GMT — topic operation stalled
While leaving the library, a topic operation appeared to become stuck in the interface.
Caddy recorded two HTTP/3 requests to POST /t/13515/merge-topic:
- 10:58:16: status
0, duration approximately 0.15 ms. - 10:58:41: HTTP 200, duration approximately 595 ms.
The successful request also appears in nginx as topics/merge_topic, HTTP 200.
This confirms that a later request was processed successfully, but does not establish why the earlier request ended without a completed response.
12:26 GMT — PWA loading problems
While in a lecture theatre, I was unable to load the PWA normally.
Caddy recorded four HTTP/3 requests for the main Discourse JavaScript bundle, completing between 12:27:05 and 12:27:42.
All returned HTTP 200 and logged 627,219 response bytes, but their durations were approximately 31.4, 27.1, 29.4 and 17.3 seconds.
The same resource normally completed in under a second, both before and after this interval.
12:42 GMT — further PWA loading problem
Another HTTP/3 request for the same JavaScript bundle took approximately 24.3 seconds.
At 12:42:41, Caddy also logged an incomplete HTTP/2 reverse-proxy response:
aborting with incomplete response
writing: write tcp ...: connection reset by peer
The upstream was the existing Unix socket to nginx. The error occurred while Caddy was writing towards the client-facing TCP connection, rather than being an identified Unix-socket failure.
The logs cannot establish whether the reset was initiated by iOS or by network infrastructure between the client and VPS.
I did not manually change the iPhone’s network settings during the two lecture-theatre incidents.
Relevance to the original report
I appreciate that these loading and topic-operation problems may have a different cause from the original Save Edit issue.
However, they demonstrate that the iOS PWA has encountered substantial request delays and an interrupted response in circumstances where I rely on it for editing notes.
My main question remains whether the composer is expected to preserve and make unsaved text accessible when a Save Edit request stalls, rather than leaving it inaccessible behind the Saving state.
I would be grateful for any guidance on useful client-side diagnostics or intended composer recovery behaviour.