I am using the QuickBlox third party framework in my application.when i am using that application we added the framework but unfortunately it is saying that "file not found". I searched so many procedures and also i followed the same way how they explained. Still i am not able to getting the success the build
Please any one help me to resolve this error.
I am waiting for your valuable answers,Please respond quickly.
Related
I have created an SDK(framework) in Objective C, which can be integrated by other third-party apps.
My SDK uses Firebase's MLVision, MLVisionFaceModel, and other features. While integrating with any third-party app, that other app must use the Firebase framework. The SDK integration works fine when a third party app uses CocoaPods for Firebase.
But the issue occurs when I try to use Carthage instead of CocoaPods for Firebase. With Carthage, I see library loading issue at run-time. I get an error message like below.
dyld: Library not loaded: #rpath/MyFramework.framework/MyFramework
Referenced from:
/Users//Library/Developer/CoreSimulator/Devices/A3651DD6-F31D-4866-963F-12A57C575BEC/data/Containers/Bundle/Application/B4D47B47-16B0-42EC-8321-5BFD7D58DD45/FaceRectCarthage.app/FaceRectCarthage
Reason: image not found
I have been trying to solve this issue for many days, but couldn't find any solution for it. Other people have also reported similar issues at Github.
https://github.com/firebase/firebase-ios-sdk/issues/1862
It is also mentioned that the Carthage distribution is still experimental.
https://github.com/firebase/firebase-ios-sdk/blob/master/Carthage.md
Now I am really not sure whether there is any solution for my problem available or not.
I am really bound to use Carthage only for one of my projects. CocoaPods is not an option for me for that particular project.
Can anyone please help me with this? Any help would be appreciated.
Firebase is distributed as static frameworks and can not be linked into dynamic frameworks.
Firebase either needs to be linked directly into the app or MyFramework must be linked statically instead of dynamically.
By the way, if you make your own SDK and someone adds an exception where there is an error, you can jump to the source code in the SDK. For example, if someone integrates your SDK but does not add a bundle package, it will report an error when integrating and jump to the source code in the SDK. How can you set the SDK to report an error but not jump to the source code in the SDK
If someone make critical error with integrating your SDK, best way make exception with correct description (e.g. with link to issue/guide in github).
This is better than getting unstable behavior. Do not be afraid crash, if it is clear.
Btw you can check debug mode and make crash only in debuging
My xamarin.ios build has been rejected from the app center due to reference of HEALTHKIT framework. I can't set linker to SDK framework only because of some 3rd party liberary. Also, I have uploaded a nee build with mtouch parameter "--linkskip=HealthKit", still my app got rejected 2nd time. Can anyone please guide me what more cahnges need to be done to remove the reference of HEALTHKIT framework from the application. Amy suggestion will be helpful
I had this recently, also tried what I could find online with no luck.
I used grep on the mac to find the said references :
$ strings directory/Payload/UpCarePro.iOS.app/UpCarePro.iOS | grep Health
And then I removed packages one by one and rebuilt the project to find the one referencing it, once I no longer found any health reference in my project, I was able to pass Apple verification.
I had no new package causing this, and my app could pass the verification process many times before that, so I don't really understand how it started, but that's how I got rid of it.
I hope this helps.
I can use this library for Android with success but failed to use it in IOS. I have followed the official notes for installing this library and then install XMPPFramework pods and react-native-xmpp pods. But after that still I get one of the following errors:
Either I get core data model not found errors issue#90 [total 6 errors] or
XMPPframework.h not found error - According to me, this errors is due to the same name collision of the XMPPFramework.h file found in the XMPPFramework and RNXMPP folder or
I get errors in KissXML Framework or
At last, if I mange to remove all the above errors, then I get the 'Linker failed error'.
Please help to provide the detailed documentation to use this library or if there is any alternative library for XMPP chat client that can be used in react-native for IOS. I have spent more than 2 weeks for searching the right solution for this.
2 month ago I had the same task and then chose a xmpp.js which I actually use on 3 environments in parallel right now:
React Native
Native Script
Node.js
On React Native it works under iOS/Android
It does not use any 3rd party native code like react-native-xmpp lib (e.g. XMPPFramework for iOS), so it's only pure JS. Did not have any noticeable issues while integrating it, so can recommend to try
The complete step by step guide on how to use XMPP lib in React Native app is available here https://medium.com/#connectycube/xmpp-real-time-chat-in-react-native-8d6d5d23dd47
I'm trying to use libraries in a project. The one i'm using is blackberry's Advanced UI sample library, which i added by creating a jar of it and preverifying it.
The code works fine, no issues.
However, I need to include facebook and twitter integration.
I'm trying to use facebook sdk 0.8.25 (requires log4b.jar) and twitter ME API 1.8.
I include them in the build path and tick for them to be copied at build.
When i run the application i get
Error starting --- Module --- has verification error 2644 at offset 08e5
I've tried each jar separately, log4b give the same issue stating error 190.
any idea what i'm doing wrong?
Managed to fix my own fault with the help of this link
http://lwuit.blogspot.com/2009/01/rim-blackberry-verification-errors.html
Basically the device is os6, and the build library was 7.1 which wasn't as issue before.
But it seems the imported libs were trying to use the 7.1 api.