Skip to content

Commit fc4682e

Browse files
committed
build: move SentryObjCBridge to Sentry target
Move SentryObjCBridge.swift from SentryObjC target to Sentry target to avoid module conflicts. When Swift code was in SentryObjC, it could see both the SentryObjC module and Sentry module definitions of the same types (SentryUser, SentryOptions, etc.), causing compilation errors. Architecture is now: - Sentry.framework: SDK + SentrySDKInternal + SentryObjCBridge - SentryObjC.framework: pure ObjC with forward declarations At link time, SentryObjC calls resolve to implementations in Sentry. Also: - Fix bridge imports (can't import Sentry when inside Sentry module) - Add SentryObjC.xcframework to gitignore - Update Ruby script to not include bridge in SentryObjC target
1 parent d44c00f commit fc4682e

4 files changed

Lines changed: 216 additions & 1193 deletions

File tree

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,7 @@ Sentry-Dynamic-WithARM64e.xcframework*
111111
SentrySwiftUI.xcframework*
112112
Sentry-WithoutUIKitOrAppKit.xcframework*
113113
Sentry-WithoutUIKitOrAppKit-WithARM64e.xcframework*
114+
SentryObjC.xcframework*
114115

115116
current_package_diff.patch
116117

0 commit comments

Comments
 (0)