Skip to content

Fix iOS Simulator build for UE 5.6+#1403

Draft
microneo wants to merge 1 commit into
getsentry:mainfrom
microneo:fix/ios-simulator-xcframework
Draft

Fix iOS Simulator build for UE 5.6+#1403
microneo wants to merge 1 commit into
getsentry:mainfrom
microneo:fix/ios-simulator-xcframework

Conversation

@microneo

Copy link
Copy Markdown

Changelog:

  • Switch to Sentry.xcframework.zip containing both device and simulator slices
  • Keep Sentry.embeddedframework.zip with UPL embedding for older UE versions

Description:

When building an Unreal project for iOS Simulator, the build fails because
Sentry.embeddedframework.zip contains only an arm64 iphoneos slice with no
simulator slice included.

Build command:

Engine/Build/BatchFiles/Mac/Build.sh ProjectName IOS Development -Project=ProjectName.uproject -Architecture=iossimulator

Error:

ld: building for 'iOS-simulator', but linking in dylib (.../UnzippedFrameworks/Sentry/Sentry.embeddedframework/Sentry.framework/Sentry) built for 'iOS' clang++: error: linker command failed with exit code 1

#1396

* Switch to Sentry.xcframework.zip containing both device and simulator slices
* Keep Sentry.embeddedframework.zip with UPL embedding for older UE versions
@microneo

Copy link
Copy Markdown
Author

Unfortunately, after integrating Sentry.xcframework.zip from this PR, I ran into an TestFlight rejection:

ITMS-90338: Non-public API usage.
The app references non-public selectors in <AppName>: removeDataForKey:

I opened a corresponding issue in sentry-cocoa:

getsentry/sentry-cocoa#7942

It looks like removeDataForKey: comes from Sentry Cocoa 9.13.0 and is present in the final binary when the new Sentry.xcframework is bundled with the Unreal plugin.

The simulator fix works, but this may block TestFlight/App Store uploads until sentry-cocoa renames that Objective-C selector or provides a fixed XCFramework.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant