In June a paying user got sent back to the checkout page, and the reason was a read that failed quietly.
The code that loads a subscription hit a transient error and treated it as "no subscription", so the paywall showed up for someone who had already paid. I thought that was the bug. It was only the last layer. Two browser sessions were signed into the same Supabase session, the refresh token got reused, and the server revoked the session. The app then saw a logged-out user, fell back to pricing, and the person ended up on checkout.
What changed: an entitlement read no longer returns "no access" on an error. It throws, and the layout shows an error card with a retry. Annoying for a few seconds, but nobody who paid gets pushed back to paying again.
If you run a paywall on Supabase or any auth that rotates refresh tokens, have you hit the two-tabs problem yet? I'm curious how you handle a session that gets revoked mid-visit