Expo Managed Workflow Crashes On Startup for iOS.

Description Installed “@stripe/stripe-react-native”: “0.2.3” through expo install @stripe/stripe-react-native. The problem is that once I eas build my expo app for simulator, the application crashes on load. I have a managed workflow expo application where i am running a react native application.

To Reproduce Steps to reproduce the behavior:

1. Create react native app with expo
2. Import the StripeProvider and add the publishableKey
3. run eas build -p ios --profile preview with correct simulator configuration as mentioned below
4. drag and drop the file to a simulator

eas.json file: { "cli": { "version": ">= 0.51.0" }, "build": { "development": { "developmentClient": true, "distribution": "internal" }, "preview": { "ios": { "simulator": true }, "distribution": "internal" }, "production": {} }, "submit": { "production": {} } }

Expected behavior The screen will crash on load

**Smartphone **

• Device: iPhone 12 Simulator --> Same thing happens if pushed to testflight

Additional context I have been trying to write to stripe customer service as well as calling in to them, but all they tell me is to wait. I have a case open for more then 2,5 weeks and I am in production already using stripe.js, but most of my payments are failing in there.

[widjesh]

This is the complete stack trace when i run expo run:ios with 5.0.4 version of expo-cli

`⚠️ Pods/boost-for-react-native: iOS@8.0 deployment version mismatch, expected >= 9.0 <= 14.4.99 Capabilities for Signing & Capabilities may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the reactnativestripe editor. (in target ‘reactnativestripe’ from project ‘reactnativestripe’)

› 3 error(s), and 2 warning(s)

Failed to build iOS project. “xcodebuild” exited with error code 65.`

[charliecruzan-stripe]

Not sure what you mean by that 🤔 the errors in the logs @widjesh shared indicate maybe an unexpected swift or xcode version, whereas your error indicates that your credentials, specifically your provisioning profile for your Notification Service Extension, are invalid