Appboy / appboy-ios-sdk

Public repo for the Braze iOS SDK
https://www.braze.com
Other
165 stars 142 forks source link

BUG: XCFramework #292

Closed jesusmateos1234 closed 3 years ago

jesusmateos1234 commented 3 years ago

using 4.0.2 precompiled framework "https://github.com/Appboy/appboy-ios-sdk/releases/download/4.0.2/AppboyKitLibrary.xcframework.zip" in build time i get this error:

Undefined symbols for architecture x86_64: "_OBJCCLASS$_ABKModalWebViewController", referenced from: objc-class-ref in libAppboyKitLibrary.a(ABKURLUtilities.o) ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1

Please check this

Bucimis commented 3 years ago

Hi @jesusmateos1234,

Using XCFrameworks in a manual integration is not supported right now. For manual integration, download Appboy_iOS_SDK.zip, which uses static libraries.

If possible, we recommend using our Swift Package Manager or Cocoapods integrations, which do use XCFrameworks.

jesusmateos1234 commented 3 years ago

Hi @Bucimis could you include manual integration from precompiled assets like other repositories (FaceBook for ex)? Appboy_iOS_SDK.zip doesn't work because depends on private search path sdwebimage installed with cocoapods.

Bucimis commented 3 years ago

@jesusmateos1234 Thanks for the feedback, we're taking a look into overhauling our manual+SDWebImage integration. In the meantime, our framework option (See Appboy_iOS_SDK.framework.zip in https://github.com/Appboy/appboy-ios-sdk/releases/tag/4.0.2) may work for you - you can simply add the Appboy and SDWebImage frameworks directly into your Xcode project as embedded frameworks. Note that our frameworks don't contain m1 arm64 slices.

jesusmateos1234 commented 3 years ago

@Bucimis How much you believe that it could be done?

Thanks for all

Bucimis commented 3 years ago

@jesusmateos1234 I'm confident the embedded framework approach works

hokstuff commented 3 years ago

Are you still experiencing this issue?

hokstuff commented 3 years ago

I'm closing out this issue due to inactivity. If the workaround described above doesn't work for you, feel free to contact us through the Support channels with more information about your integration steps. Thank you!