Open nicolasmelo1 opened 2 years ago
These frameworks are universal binaries so you'll need to either strip the Simulator build to get the required iOS framework or you can mark Validate Workspace to Yes to build successfully. Also you'll have to mark Enable Bitcode to No. These config you can find in Build Settings.
You would need to extract the binaries from these paths (ref. attached images) and link it in your new framework, then you should be able to use it.
Oh nice,
Thanks for your response, so, since i've read your message i've been trying to make it work but still without any success. One thing that i've noticed is that you compiled Test to a Test framework, can't i compile the source code to a static library?
it's still giving me this error:
Failed to build iOS project. We ran "xcodebuild" command but it exited with error code 65. To debug build logs further, consider building your app with Xcode.app, by opening ModuleExample.xcworkspace.
Command line invocation:
/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace ModuleExample.xcworkspace -configuration Debug -scheme ModuleExample -destination id=F364796E-5140-4CFD-ADE9-4CF794593068
User defaults from command line:
IDEPackageSupportUseBuiltinSCM = YES
note: Using new build system
note: Planning
Analyze workspace
Create build description
Build description signature: 9f60adfb6c57f9623891d49963e10757
Build description path: /Users/nicolasmelo/Library/Developer/Xcode/DerivedData/ModuleExample-cdzaxfvrbkxfyechcpvzbzeijktn/Build/Intermediates.noindex/XCBuildData/9f60adfb6c57f9623891d49963e10757-desc.xcbuild
note: Build preparation complete
note: Building targets in dependency order
warning: Capabilities for Signing & Capabilities may not function correctly because its entitlements use a placeholder team ID. To resolve this, select a development team in the ModuleExample editor. (in target 'ModuleExample' from project 'ModuleExample')
/Users/nicolasmelo/lc-workspace/react-native-module/example/ios/ModuleExample.xcodeproj: error: The linked library 'libPods-ModuleExample.a' is missing one or more architectures required by this target: x86_64. (in target 'ModuleExample' from project 'ModuleExample')
2022-08-01 10:08:23.829 xcodebuild[5150:835888] 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
2022-08-01 10:08:23.829 xcodebuild[5150:835888] 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
** BUILD FAILED **
Here is the source code, it's really simple stuff just to test.
Bug Report
TL.DR.: When i compile my custom library it compiles, but when i try to use the library i've created on a real app, the app does not compile. And it really seems with WebexSDK package because with other packages/pods it works.
π Search Terms
react native webex sdk, webex ios sdk as package, extract ios webex
π Version & Regression Information
3.5.0
π Tool Used
Macbook Pro 16GB M1
π» Code
I Have tried installing FBSDKCoreKit in the .podspec and it compiled and worked as expected. Then when i removed the FBSDKCoreKit and installed WebexSDK it gave me an error when running the code. This one is when installing WebexSDK library on the .podspec file https://youtu.be/NeP2NX6cjGA
π Actual behavior
I'm getting this error on the console:
It is strange because FBSDKCoreKit works and WebexSDK don't. It's important to say that on both cases i'm not even importing any of those SDKs on the code. I'm just adding WebexSDK to the podspec and compiling, there is no single code there.
What we are trying to do is create a library that we could reuse in our projects that have WebexSDK inside of it, it looks like WebexSDK cannot be compiled in a separated source from the app, it's meant to be used and compiled on the app. This is really bad for us because it means that if we want to use the SDK on two distinct apps we need to CTRL+C and CTRL+V the code. Which is definetly not ideal.
π Expected behavior
I want to be able to compile WebexSDK without the app so i can extract the logic in a single library than can be reused by everyone in the team and the company. Right now the problem really seems on WebexSDK