I am attempting to run the sample developer dji application for the iOS platform via Xcode version 13.2.1. Upon building the application for the ObjectiveC and Swift sample code, I get an error indicating "Library not found for -lDJIWidget".
mac os: 12.2.1
I am a new macOS user, and this is my first time learning to build an iOS application for DJI. How can I resolve this error?
Trouble shooting steps taken
ensure cocoapods is installed for both sample codes (objectiveC and swift code)
use the <Project>.xcworkspace file for setting the bundle identifier and app key
Connect your ios device to your computer and run the build off of it.
Related
I'm trying to integrate the AppsFlyer SDK into my SwiftUI iOS app. I've installed the framework via cocoapods.
But now when running the app (My Mac, Designed for iPhone), I get this error:
The developer of this app needs to update it to work with this version of macOS.
Failed to verify code signature of /var/db/appinstalld/Library/Caches/com.apple.mobile.installd.staging/temp.rxLc7F/extracted/panicdiary.app/Frameworks/AppsFlyerLib.framework : 0xe8008029 (The code signature version is no longer supported.)
I also get a different error telling me: 'Unable to install" when trying to run on my iOS device.
How can I remedy this?
I am building an iOS application which is using Agora iOS SDK pod 'AgoraRtcEngine_iOS' version 3.3.2
When I run application using real device it is working fine. But when I build application using simulator it gives an error:
Framework not found AgoraAIDenoiseExtension
My laptop has Apple M1 chip and OS Big Sur version 11.2
Please help!
I solved this issue by adding AgoraAIDenoiseExtension.xcframework file in Frameworks and Libraries
Steps to follow:
Select your project
Go to General Tab
Go to Frameworks and Libraries and click on + button.
Add respective framework files
Clean and Run your project
I see that you've solved it with a temporary fix Dalijeet, but another solution would be to use swift package manager here:
https://github.com/AgoraIO/AgoraRtcEngine_iOS
I just started working on an already existing React-Native app that needs a really small update, but that has not been updated since October 2019.
The first thing I need, in order to start updating it, is to build the app. That is where I cannot find a way to do it.
At the moment, I’m trying to build the app only on iOS and not on Android.
First of all the current toolset versions I’m using are:
React-Native version: 0.53.3
Xcode version: 11.4.1
iOS SDK: 13.4
Node version: 8.16.6
NPM version: 6.14.1
I initially had problem with third-party tools, but I managed to fix it through manually installing them in the node-modules/react-native folder.
Now I’m getting errors about Xcode not finding headers of the modules the app is using
like, for example,
React/RCTViewManager.h file not found
Or, similarly, the GoogleSignIn.h headers in the RNGoogleSignIn module
I believe it’s just an error of how libraries are imported in Xcode, because as a test I have created a new react-native “test app” with the same exact versions of react-native and node, then I installed the core dependencies needed to perform the update on the original app, and I managed to build it without problems.
I’ve also tested building the app on an old Mac with macOS 10.14, using Xcode 9, but I’ve got different errors, always related to importing headers of modules.
This is the toolkits versions of the “old Mac”:
React-Native version: 0.53.3
Xcode version: 9.4.1
iOS SDK: 11.3
Node version: 8.16.6
NPM version: 6.14.1
Searching online I know that some of the problems I have faced (like the third-party react-native manual install) have been fixed in react-native updates, but I’m not expert enough with the technology to be sure that I can handle the update process without introducing bugs. I would prefer to just make this version run for now and facing the updating process later.
Do you have any suggestion of things about what I can do in order to successfully build the app?
If anyone ever comes here with a similar problem: the solution was pretty simple.
Be sure you're using the .xcworkspace file in your iOS folder, and not the .xcodeproj. This is used to automatically (and correctly) load the Pods dependencies in Xcode without having to manually link them.
Be sure that you installed the dependencies correctly with the right version of Cocoapods. We had to use an old version (1.5.x) that would automatically downloaded some pod dependencies. Our error was due to Facebook SDK. Newer versions of cocoapods did not download it, while the 1.5.x version would download it.
Good day.
I'm trying to use Qt to develop an application for iOS.
I using macOS Mojave 10.14.5 and xCode 10.2.1 (installing from the AppStore).
Qt Creator - version 4.7.2 & qt - version 5.11.2 (also i tryed use Qt Creator - version 4.9.1 & qt - version 5.12.3). I create simple application "Qt Widget", and trying build his. I get the only error:
error: [xcodebuild-debug-simulator] Error 64
I inspect my kits and virtual devices, but they configured correctly:
Also, I can start any virtual device and it loading successful:
Why appears this error? Thank.
P.S. sorry, possibly my English language not quite correctly.
P. S. S. :I install macOS on VMware Workstation 15.
UPD1:
I created simple app from Xcode, and app is running successful.
I compile app in Qt Creator, but I run app from xcode, and app started successful. There were complaints about Bundle version
and Bundle version string short, I corrected them in the file Info.plist.
Scenario:
I have updated to Qt 5.9.6 and I have Xcode 10.0 running on High Sierra.
I have a Qt App that builds for OSX and iOS. And it builds and runs all well with Qt 5.9.4.
Now, I want to update to 5.9.6 for a reason. When I try to build for iOS using Qt 5.9.6, I get the following error
Project ERROR: This mkspec requires Xcode 4.3 or later
Question:
Is there a way to get around this issue?
Note that the OSX build using Qt 5.9.6 just works fine. I have QMAKE_IOS_DEPLOYMENT_TARGET set to 10.0 for iOS case
PS:
I also deleted the .qmake.stash and the .pro.user file from the root directory and restarted QtCreator to try build from a a fresh start. But still get the same issue!
This is bug in Qt, use Qt 5.9.7 where this bug is fixed.