After installing the OneSignal library in an ejected app through the Bare Workflow, I’m having some trouble building the .ipa for a TestFlight submission.
The OneSignal installation requires creating an extension. Since I’m using Expo Application Services, and therefore the
eas build --platform ios command to build my app, I get the following output.
// ♥ eas build --platform ios ★ firstname.lastname@example.org is now available, please upgrade. Proceeding with outdated version ✔ Linked to project [redacted] ✔ Using remote iOS credentials (Expo server) If you provide your Apple account credentials we will be able to generate all necessary build credentials and fully validate them. This is optional, but without Apple account access you will need to provide all the values manually and we can only run minimal validation on them. ✔ Do you want to log in to your Apple account? … yes › Log in to your Apple Developer account to continue ✔ Apple ID: … [redacted] › Restoring session [redacted] › Team [redacted] › Provider [redacted] ✔ Logged in Local session ✔ Bundle identifier registered com.open.baton ✔ Synced capabilities ✔ Fetched Apple distribution certificates Wrong bundleIdentifier found in provisioning profile; expected: com.test.sample, found (in provisioning profile): com.test.sample.OneSignalNotificationServiceExtension ✔ Fetched Apple provisioning profiles ✔ Generate a new Apple Provisioning Profile? … yes ✔ Created Apple provisioning profile ✔ Created provisioning profile Project Credentials Configuration: Project: [redacted] Provisioning profile (ID: [redacted]) Apple Team ID: [redacted] , Apple Team Name: --------- Distribution Certificate - Certificate ID: [redacted] Apple Team ID: [redacted] , Apple Team Name: --------- All credentials are ready to build [redacted] ✔ Uploaded to EAS 2s Build details: [redacted] Waiting for build to complete. You can press Ctrl+C to exit. ✖ Build failed Error: Standalone build failed!
Here’s the output after running
Expo CLI 4.0.17 environment info: System: OS: macOS 11.1 Shell: 3.2.57 - /bin/bash Binaries: Node: 14.5.0 - /usr/local/bin/node Yarn: 1.21.1 - /usr/local/bin/yarn npm: 6.13.7 - ~/.npm-global/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.10.0 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.3, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2 IDEs: Android Studio: 4.1 AI-201.8718.104.22.16853283 Xcode: 12.3/12C33 - /usr/bin/xcodebuild npmPackages: expo: ~40.0.0 => 40.0.0 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: ~0.63.4 => 0.63.4 react-native-web: ~0.13.12 => 0.13.18 react-navigation: ^4.0.10 => 4.0.10 npmGlobalPackages: expo-cli: 4.0.17 Expo Workflow: bare
For some reason, I keep getting this message:
Wrong bundleIdentifier found in provisioning profile; expected: com.test.sample, found (in provisioning profile): com.test.sample.OneSignalNotificationServiceExtension
For those who have ejected into the Bare Workflow and have installed either OneSignal or a library that creates an extension in Xcode, how have you navigated using Expo to continue to build your projects? Is this possibly a bug with Expo Application Services?
Thanks in advance for your help!