Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

I have a SPFx React application where I am printing the HTML page content using the javascript default window.print() functionality. Once I save the page as pdf from the print preview window and open it using Adobe Acrobat, the links(for eg -> Google) within the content are not clickable and appearing as plain text. I have tried to print random pages post searching with any keywords in Google and saved the files as pdfs, but, unfortunately, the links are still not clickable there as well. To check whether it is an Adobe Acrobat issue, I have performed the same print functionality from Android devices and shared the pdf file across the iOS devices and in that case, when opened using Adobe Acrobat, the links are appearing to be clickable. I am wondering whether it is something related to how the default print functionality works for iPadOS and iOS devices. Any insights on this would be really helpful. Thanks!!! Note: The links are clickable for MacOS as w

Seeing these when trying to create an xcframework for Apple Silicon that supports Mac Catalyst and the iOS Simulator: Both ios-arm64-simulator and ios-x86_64-simulator represent two equivalent library definitions. Both ios-arm64-maccatalyst and ios-x86_64-maccatalyst represent two equivalent library definitions. Here's the command: xcodebuild -create-xcframework tt-framework ./xcframework-build/catalyst-x86_64/opencv2.framework tt-framework ./xcframework-build/catalyst-arm64/opencv2.framework tt-framework ./xcframework-build/osx-x86_64/opencv2.framework tt-framework ./xcframework-build/osx-arm64/opencv2.framework tt-framework ./xcframework-build/iphonesimulator-arm64/opencv2.framework tt-framework ./xcframework-build/iphonesimulator-x86_64/opencv2.framework tt-framework

To support Action extension, have created an embedded framework so that all common code can be there. Have moved Localizable.strings to embedded framework so that have single locazaiton file for both app and extension. But when tested I only see english (development langage ) being used. I am using following call.NSLocalizedString(key, bundle: <bundle>, comment: <comment>)

I have a Framework built as a shared Framework from a collection of static libraries. Let's call it Framework A. I have a built iOS application that contains symbols B, and C. Framework A is built calling references to function B and class C, with -Wl,-flatnamespace,-undefined,dynamiclookup as linking flags. The built iOS application crashes: dyld: Symbol not found: OBJCCLASS$MyClassC Expected in: flat namespace The iOS application contains MyClassC and an objdump -t shows this. Both the framework and iOS app are built with -flat_namespace. Is this possible to resolve without moving objects B and C into the framework? When built as a static library prior to conversion, the framework has no issues.

Hi all, I'm having the following issue with objc/swift interoperability and I'm hoping you can help me out, I'm trying to use a swift class from a framework, in my app target, however they're not in the same project, the framework is built and then added to the other project manually. So I have a huge project (InStore), that has three targets, two frameworks (InStoreCore, InStoreML) and an App Target (this is the test app for the frameworks). InStoreML has a dependency to InStoreCore, both of which have swift AND objc code. If I try to use a swift class (ISAppBehaviour) from obj in the test app target of that project, it all works just fine, for simplicity's sake I'll put an example. #import /*...*/ @implementation ISExampleViewController (void)viewDidLoad { [ISAppBehaviour class]; } /*...*/ @end That compiles just fine, I am able to reference the swift class (ISAppBehaviour) from objc in the app target. The issue comes when I try to use those frameworks

I'm starting with a working app, and trying to encapsulate as much functionality as possible into an embedded framework. Everything in the embedded framework is Obj-C or C, and the new 'skeleton' project is Obj-C.I believe I'm building my framework so that it defines a Module with a particular name.I've used nm against the framework contents and believe my custom class is implemented in there, the symbols weren't stripped out.The umbrella header for the framework specifies ALL of the headers that used to go into the working app target, even AppDelegate.h.I believe I've updated my Storyboards so that the Module field for each custom view controller specifies the Module name, and have inspected Main.storyboard to confirm that my intended custom class name and module name are reflected in the XML source.At runtime, I get a variant of unknown class in interface builder file. Unknown class _TtC8<moduleName>25<customClassName> in In

Greetings all, I have a crash report but I cannot figure out what is causing the crash. When I do a debug build on simulator, it is all good. When I make a release build and install on device, it crashes as soon as the mobile app opens. I am using React Native 0.73.2 if that helps at all. Any help understading this crash report is appreciated. Flex-2024-01-31-092208.txt

I have a framework that links another framework (my framework has classes that wrap some things in a third party framework).If any class in my main app tries to use a class from the framework inside another framework, the linker fails with undefined symbols. But everything public in the framework inside of the framework should be public.Any ideas how I can resolve this?Thanks