Here is the error message:
I checked this solution, but my paths already have that value in Xcode:
Build is failing in iOS #447
The tipsi-stripe library is no longer maintained or supported by the developers. You should instead use the official stripe-react-native library following the migration guide.
Related
I have integrated IBM Trusteer to the ios app we have created using IBM Mobilefirst Cli 7.1 by following the turtorial : https://mobilefirstplatform.ibmcloud.com/tutorials/en/product-integration/7.1/trusteer-ios/
Now , I am getting error shown in the screenshot:
Please help me resolve this problem.
According to the screenshot, it is complaining about libtas_phonegap_plugin.a. I can't say why it's complaining, but I can tell you you do not need this file at all. According to the tutorial you linked to, you need libtas_full.a, not the "phonegap" file.
See also: http://onebigfunction.com/ios/2015/03/15/invalid-bundle-structure/
You may have placed the libtas_phonegap_plugin.a file inside a folder instead of just including it it in the list of linked libraries.
I am opening an external URL in my Swift app using the line:
UIApplication.sharedApplication().openURL(url)
This was working fine until I added Realm to my project via CocoaPods. At that point, it started giving me the two compile errors below:
'sharedApplication()' is unavailable: Use view controller based
solutions where appropriate instead.
'openURL' is unavailable
These errors indicate that the API is unavailable to Application Extensions, but my code is in a normal application, not an extension. Why would adding Realm result in the compiler thinking it's in an App Extension?
You can't use sharedApplication from an app extension.
But note that the apple documentation states:
IMPORTANT
Apple allows any Today widget to use the
openURL:completionHandler: method to open the widget’s own containing
app.
ExtensionOverview.
This is an issue that can occur when adding Realm to a project that is using a version of CocoaPods prior to v0.39. To fix it, update to the latest version of CocoaPods using:
sudo gem install cocoapods
This problem is due to CocoaPods issue #3906, which results in portions of Realm's configuration settings being applied to your application's targets. One of the settings that Realm enables is "Allow app extension API only", which is why you end up seeing this particular error.
I still have the same issue, even with CP v1.8.3.
A quick fix is to select the offending pod > Build Settings > Require Only App-Extension-Safe API > Set to No.
I get the following build error after implementing step number four "Add the Braintree SDK code to project" from the Manual Integration Without CocoaPods guide.
braintree_ios/Braintree/UI/Braintree-Payments-UI.h:3:9: 'Braintree/BTUICTAControl.h' file not found
Tested in
New Objective-C iOS app project.
In Xcode 6.1 (6A1042b) and 6.3 (6D543q)
How can I fix this build error?
I work on the Braintree iOS SDK.
I believe using the name Braintree instead of Braintree SDK for the framework target name will resolve this particular issue. I recently updated the manual docs accordingly.
We recommend that you integrate using CocoaPods if at all possible, as it handles all this complexity for you.
Note also that I've responded on the issue you posted on GitHub. Let's resolve this there. Thanks!
Have you tried manually downloading the zip file and not using git?
Try following the second bullet point from the first step.
IIRC runtime compilation and linkage to JIT-ed native code is not allowed on iOS. I was wondering does it affect native code that was not compiled on the client machine but a remote build server and deployed and linked to internally. Is the problem "native code generated on the fly" or "native code that has not passed Apple's review process"?
As I know, there's no correct way to dynamic linking in iOS - it's prohibited by Apple.
Also look here please: Can you build dynamic libraries for iOS and load them at runtime?
I'm attempting to upgrade from Facebook SDK 2.0 to 3.0 and I'm having basically the same issue as is mentioned in this thread: XCode & Facebook IOS SDK - Instructions incorrect but with a slightly different goal I think.
I'm using the instructions here: http://developers.facebook.com/docs/mobile/ios/build/
When I try to build the static library, I get a "no such file or directory" message. I checked, and sure enough, there is no build_facebook_ios_sdk_static_lib.sh file in the "scripts" directory when I try to execute it.
Here's my dilemma. We have multiple developers on the project (and some other members who basically know how to pull down and build within Xcode but that's about it), and I don't want to require all of them to install the Facebook SDK. Same for a build machine (though in that instance I suppose we could install the SDK directly on the build machine).
It sounds like building a static library has been effectively deprecated, or maybe I'm missing something, but what I really need to just get all the pertinent code into our repository, and in a form in which anyone can just pull it down and build. Is this possible with the 3.0 SDK, and if so, what would be the steps to do that?
Thanks!
For the Facebook SDK 3.1 (latest from 3.0) you should not follow the old instructions, instead check these instructions out:
https://developers.facebook.com/docs/getting-started/facebook-sdk-for-ios/3.1/