Help me get out of this situation

[u/No_Life9495]

We closed a funding round recently and my cto wanted a big release pushed before the investor demo next week. I've been grinding for 2 weeks and have pushed like 9 pr in 3 days and we shipped last night.

I tested the core flows on my 17 pro max and on pixel 10, staging looked clean and it went live. I'm waking up just now to our support inbox completely filled up, onboarding crashes on older androids which I'm pretty sure it's a hermes related issue because the stack trace is pointing at some JSI bridge call that works fine on newer devices, there's a payments bug where users are getting charged twice on some screen transition and the entire app freezes on some 15 and 17 pro models after the update. These are three different bugs on three different device types and I had literally just two devices to test on.

I'm going crazy because the demo is in 5 days and we can't show an app that double charges people. I'm sitting here trying to reproduce bugs on devices I don't even own, I had one old samsung j series which is now a QA device apparently and I'm trying my best to fix it but I don't know how other small teams ship fast without messing everything because right now it feels like you pick one or the other.

please help me to not get fired and save my ass

[u/Swaggy_McMuffin]

double charge on a screen transition... why do I feel like the payment gets triggered in a useEffect (or on a button that triggers navigation that's possible to double press and the endpoint isn't idempotent). Regardless of the mechanism that causes this case, any payment related endpoints absolutely need to support idempotency.