The Android release build is working fine without issue however the iOS is crashing when trying to run on a device.
Looking through the build logs, I’ve found a few issues.
[stderr] 2022-08-23 03:21:24.269 xcodebuild[4233:12395] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
[stderr] 2022-08-23 03:21:24.269 xcodebuild[4233:12395] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
[stderr] 2022-08-23 03:21:24.325 xcodebuild[4233:12395] XType: failed to connect - Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.fonts was invalidated: failed at lookup with error 3 - No such process." UserInfo={NSDebugDescription=The connection to service named com.apple.fonts was invalidated: failed at lookup with error 3 - No such process.}
[stderr] 2022-08-23 03:21:24.325 xcodebuild[4233:12395] Font server protocol version mismatch (expected:5 got:0), falling back to local fonts
[stderr] 2022-08-23 03:21:24.325 xcodebuild[4233:12395] XType: unable to make a connection to the font daemon!
[stderr] 2022-08-23 03:21:24.325 xcodebuild[4233:12395] XType: XTFontStaticRegistry is enabled as fontd is not available.
I’ve renewed the provisioning profile
Cleared the build cache
eas build --platform ios --profile production --clear-cache
I’m a little stuck on how to progress. Any information would be great
These errors are often false positives put out by the Xcode compiler just before or after the actual error. If you provide us a link to your build, we may be able to suggest where to look.
Well, seeing that I missed a) the link to your build, and b) the fact that it wasn’t even a build failure, let’s start over here …
I assume you’re not getting the error when running locally in development mode. One thing you can try to make your development environment simulate production a little more closely is to pass the --no-dev flag to expo start. This might catch if there’s an issue with the production build of the JavaScript that’s not present in the development build.
I recognize this. I had problems with the combination of Xcode prior to 13.3 (I believe) and iOS 12.5, might that be related? No crashes once I used Xcode 13.3 for the build (not sure which version expo 45 uses).