The Android release of my React Native app is stable, and the shared codebase already includes RevenueCat for subscriptions and Apple Authentication. On iOS, however, the current Expo EAS workflow halts with dependency conflicts that lead to a build failure. I need a seasoned Expo specialist to dig into these conflicts, explain the root cause, and get the build passing. Once the build succeeds, I’d like you to run a quick validation pass on two key features—RevenueCat in-app purchases and Sign in with Apple—so we can be confident they behave identically to Android. When everything checks out, you’ll generate a production EAS build and guide me through the final settings needed for App Store Connect submission. Deliverables • Resolved dependency conflicts so EAS completes without errors • Confirmation that RevenueCat IAP and Apple Authentication function on physical iOS devices • A clean, archived build (ipa) produced via Expo EAS, ready for App Store review, plus a concise hand-off note summarizing configuration changes and next steps If you’ve shipped apps to the App Store before using Expo’s managed workflow and enjoy detective work around native modules, let’s get this finished.