Build 8 has been with testers for six days. The most useful thing that came back this week wasn't written by anyone. It was sitting in the telemetry.
On my test account : 2,127 failed prefetch events in thirty seconds. Ten to twenty milliseconds apart. A hundred a second, from one phone.
Not a retry policy being too generous. A render loop. The guard meant to stop a second fetch while one was in flight was reading a value frozen in a closure, so it always saw "nothing in flight" and fired again. The file already knew about the trap : the right fix had been sitting in it since August, with a comment spelling it out, and two of the three call sites weren't using it.
The part that bothers me is that it gets worse the faster the failure comes back. A slow 502 throttled it to about ten attempts. Airplane mode, dead DNS, no bars, those let it run at full speed. So the person who suffers most is a tester on a bad connection, and what they experience isn't an error. It's the app feeling slow. Nobody reports slow.
Same week, the backend seized twice, on the 31st and again yesterday. Every TMDB call timing out for hours while the health check answered in 0.12 seconds looking perfectly fine. Both times a manual restart was the only thing that ended it. It now replaces its own connection pool after three consecutive stalls, so that hour becomes a minute.
One report did come from a human, and it was a good one : the guided tour on the profile screen went almost fully dark and pointed at the wrong place. Two lines in the wrong order, a rectangle clipped to the screen before being converted instead of after.
If you test apps : when something is just slow, do you say anything? Honestly, I'm not sure I would.
Source: r/ATJV · by /u/Sv3n-Sk4