The 4-test protocol that isolated a 9 ms Stripe SDK crash on Next 16 (opens in new tab)
The number that lied Friday May 15, 4:13 PM. The Sentry alert pings on my phone. The first Phase 1 re-enrolling student waits in front of the payment screen, her name at the top of my tab. I put down the can, I reopen the screen. The mug with Françoise's face on it, on the desk next door, catches a yellow reflection I notice without looking at. The stack trace fills the screen. The stack trace opens, nine fields out of ten at null, and a number I didn't see coming. type = "StripeConnectionErr...
Read the original article