I generated graphql swift files using Apollo Codegen - https://www.apollographql.com/docs/ios/code-generation/codegen-cli
But when I added files to the project then I see the duplicate swift files under the fragments folder and Schema->Objects folder.
Below is the error
Filname "XXX.grapgql.swift" used twice.
"path/customer/Fragraments/XXX.grapgql.swift"
"path/customer/Schema/Objects/XXX.grapgql.swift"
Appreciate any help to resolve this.
I'd recommend you post this issue in Apollo GraphQL official community. The team that support the iOS client regularly monitors this forum.
Related
I'm trying to integrate RSA SecurID in my existing iOS Application.
It doesn't seem to be a straightforward way of achieving this task.
Here is what i've tried so far:
The files included in the zip downloaded are the following:
Add the files inside inc folder to my project as well as the libSecurIDLib.a .
Check in build phases if the library is linked in binary .
Check in build settings if the library path is correct .
Clean and Build APP and keep getting these ugly and counterintuitive errors.
Anyone have any thoughts on why i'm having this problem.
It has anything to do with the headers?
Thanks!
You haven't added the other dependencies that are listed on page 38 of the Developer's Guide.
Specifically these errors are caused because you haven't added libxml2, but you also need libsqlite3 and the System configuration framework.
I am using GoogleSpeechRecongnization api within my project for Speech To Text.
I have copied all required files and installed pod from sample of Google for Speech To Text Api. Also copied these 2 files AudioController, SpeechRecognitionService from the Sample Code to implement the feature.
Now when I compiled my code, I received errors as in attached image.
While same steps and files are working perfectly in demo app with the custom interface, created by me.
Please help me to fix these in my main project. Thanks
The SpeechRecognitionService require google service to be linked which lies in the google folder of the sample Project, please add that too in your project, it should be working..
See where is google folder here
Cheers.
Check demo project supported architectures in build settings...
I think you need to add missing architecture in your build settings
Maybe it's in your project and maybe it's in the Pods project
I have an application written in Swift which already uses the SwiftyDropbox API.
I installed SwiftyDropbox with cocoapods and the use_frameworks! keyword.
And now, when I add this pod 'Google-API-Client' to my Podfile, I get a Duplicate definition error in my Google Drive API when I tried to build my project.
So, I've decided to follow the Google Drive guide : https://developers.google.com/drive/ios/quickstart?ver=swift
But it seems this guide is deprecated, because there is no file named GTL.xcodeproj or GTMSessionFetcher.xcodeproj in the files we download by following this tutorial. And all the steps they describes seems to be inconsistent.
So I don't know what can I do to work with SwiftyDropbox and Google Drive API in my iOS project.
Just looked into the repo, it had an update last Jan 13 that may have affected the naming of the xcodeproject.
Currently, the Step 3.b project will then be
google-api-objectivec-client/Source/GTLCore.xcodeproj
gtm-session-fetcher/Source/GTMSessionFetcherCore.xcodeproj
Hopefully this is a bit of help with importing the project.
I want to use FMDB in a swift framework. I follow this tutorial http://programmingthomas.com/blog/2014/7/23/sqlite-in-swift-frameworks but i am getting this error.
Opening import file for module 'Swift': Not a directory
I did all the steps exactly as mentioned in the tutorial.
Also i tried to import the files (not create a seperate framework) but it gives me an error saying that cannot import a non modular header file.
FYI, you can now build framework for FMDB using the master branch, and using the swiftFramework branch that I discussed below is no longer needed. (That branch was created because of a problem in Xcode 6 and 7 that prevented the creation of frameworks that referenced non-modular headers.)
For example, see issue #540 for an example of how to build the frameworks using Carthage. Note, you don't have to use Carthage, but it demonstrates that the swiftFramework branch isn't needed anymore.
I'll keep the original answer below for historical purposes, but it appears that it is no longer applicable. We can build FMDB framework without incident now in Xcode 8.
There is a FMDB branch (see swiftFramework branch) that was created to allow you to create a separate framework for FMDB. For instructions on how to use it, see Using FMDB in a framework discussion at the end of the README for that branch.
Note, this is a separate branch and has not been integrated into the master branch (and probably won't until FMDB 3.0 because it includes some trivial, yet non-backward compatible changes). So, if you don't need it in a framework, I'd suggest just adding the the source to your project directly, rather than separate framework. But if you need a framework, the above branch may help you out.
I'm using this URL to implement the App authenticity for iOS.
https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-6-3/authentication-security/application-authenticity-protection/application-authenticity-protection-native-ios/
However, I need to know where to find the worklight.plist to make sure that the applicationId is matching what i'm putting in the application-descriptor.xml.
The worklight.plist file is available only after building the MobileFirst application using the MobileFirst Studio Eclipse plug-in (or CLI commandline tool).
For Hybrid applications,
You can then find the worklight.plist file in the your-project\apps\your-app\iphone\native folder.
For Native applications,
You need to only generate the NativeAPI for iOS and it'll be located in the generated folder, in your-project\apps\your-nativeapi\WorklightAPI folder. You then need to follow the native apps tutorial to copy over this (and more) files to the Xcode project.
Thank you,
I have found it after building the project inside the native folder.