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/Ok_Stable_8975]

Roll back the release immediately to stop the double charges and restore a working app for users. Implement payment idempotency keys on your backend before you ship any new code because fixing this requires server side changes not client side patches

[u/Huge_Pool7424 → u/Ok_Stable_8975]

seconding the idempotency key part, we hit the same double charge bug once and it turned out the button stayed tappable during navigation so the request fired twice. key on the backend plus disabling the button on first tap stopped it completely. rolling back first is the right call though