Stabilize Bitrise CI/CD Pipeline

Our React Native 0.72.x app is already shipping to the App Store and Google Play, but the current Bitrise workflow (15 steps on the osx-xcode-15.4.x stack) has become fragile. The main pain point is signing reliability: builds occasionally fail to produce a properly signed IPA or AAB, forcing manual intervention and delaying releases. Here is what I need you to tackle: • Resolve iOS & Android signing so every run outputs a fully signed IPA and AAB ready for distribution. • Configure automatic build-number incrementing. • Set up seamless uploads to TestFlight and Google Play Internal track. • Refactor [login to view URL]: eliminate duplicated steps, improve overall structure, and move anything sensitive to Bitrise Secrets. • Keep everything on pure Bitrise steps (no Fastlane) and continue using the Apple Service Connection. • Deliver a concise, step-by-step README that explains the workflow for future maintenance. This is a stabilization job, not a fresh setup, so I’m expecting minimal disruption to the existing pipeline while you make it dependable. If you’ve solved similar production issues before, especially on Bitrise, please share a brief example or two when you respond—links, screenshots, or a short description of your previous CI/CD fixes are perfect. Looking forward to finally having a release process I can trust.

Projektin tunnus (ID): 40252251