[Bug]: iOS TestFlight thread view — header and usage-limit banner overlay message content #15652

Activity

1. juliusmarminge commented on Oct 4, 2026

   

   juliusmarminge

   on Oct 4, 2026

   Member

   More actions

   Note

   Grok responding on behalf of Julius.

   Triage

   Thanks for the report and the screenshots, @alhassanaraouf. They line up closely with the code on main for the thread screen.

   What I found

   I see two separate causes behind the overlap.

   Header. The bar is transparent by design. It uses the liquid-glass setup in apps/mobile/src/Stack.tsx (headerTransparent plus UIKit's automatic scroll-edge effect), so content is meant to scroll under it and fade at the edge. The thread list deliberately doesn't set a manual contentInset (ThreadFeed.tsx) so that fade has room to render. In your screenshots the fade isn't happening: message text stays fully readable behind the back button, title, and toolbar. That's the bug in this part.

   Usage-limit card and composer. UsageLimitRecoveryCard is mounted inside the absolutely positioned composer overlay in ThreadDetailScreen.tsx, above ThreadComposer. Its measured height is only applied as an end inset, which pads the bottom of the scroll content, so rows in a long thread still scroll under the card. The composer under it uses a gradient from fully transparent to mostly opaque (from-screen/0 via-screen/60 to-screen/90 in ThreadComposer.tsx), so the last rows show through. On web, the same recovery notice sits in the in-flow composer banner stack, so the transcript stops above it.

   The report has enough detail to reproduce: open a long thread, scroll it, and put the thread into the usage-limit state so the amber card shows.

   Likely fix area

   • Header: the scroll-edge fade between Stack.tsx and ThreadFeed.tsx, so content actually fades under the glass bar. An opaque bar would be a separate design change.
   • Usage-limit card: one option is to make the card's height shrink the visible list instead of only padding the end, which is how web places it. Another is to move it into the in-flow layout.
   • Composer: the opacity of the gradient where it overlaps the last transcript rows.

   A maintainer will decide on the fix direction.
2. juliusmarminge

   added

   bugSomething is broken or behaving incorrectly.Something is broken or behaving incorrectly.

   via-triageFiled through npx t3 triageFiled through npx t3 triage

   on Oct 4, 2026
3. alhassanaraouf commented on Oct 14, 2026

   

   alhassanaraouf

   on Oct 14, 2026

   Author

   More actions

   fixed
4. alhassanaraouf

   closed this as completedon Oct 14, 2026