I need to integrate Google+ iOS SDK using Cocoapods but the link provided doesn't have any information about an official pod.
I searched and found official pods by Google but there is no sign of the G+ SDK. Then I found this pod and I'm not sure if it is safe to use or not as it is not maintained by Google.
If you look at the version you provided in the first link, the name of the file itself contains 1.7.1. The version on the CocoaPods site is marked as 1.7.1. That's a good sign.
None of the people mentioned as maintainers of the pod are actually working in Google. That's a bad sign. At this point we don't know anything.
So after certain searching online, you'll find that the podspec, in fact, is in this repository. It is somebody else, who takes Google's code and puts it into his repo on GitHub.
Answers for you:
Is it safe? Probably yes, but it's not 100%. The code is visible in public repo, so the chances are really high that it is safe.
Is it maintained by Google? Nope.
Related
I am using Evernote APIs to create custom notepad and as per process I install the cocoapod the the ever note and follow all the steps given in documentation Evernote Documentation. When I goes to use it EvernoteSDK is not included.
No classes from evernote are visible for me.
It seems you are pointing to the old documentation. try the new one here.
It is very simple if you have cocopods file, add:-
pod 'evernote-cloud-sdk-ios'
Since Microsoft's WinObjC is still under development, they have not supported third party library like AFNetworking. Is there any other way around to use already existing AFNetworking in iPhone. And, is Pods supported in the latest WinObjC library?
I work on the iOS bridge project at Microsoft. AFNetworking isn't currently supported so you won't be able to reuse those parts of your codebase at the moment, but it's a big priority for us and we're looking to add support in the next few months. You can see our current roadmap here:
https://github.com/Microsoft/WinObjC/wiki/Roadmap
We also don't currently support CocoaPods since our clang compiler front end doesn't support virtual filesystems, which CocoaPods depends on. Again, this is a feature request we get a lot so it's a top priority for us.
Thanks for checking out the project – if you have any other questions, comments or suggestions, feel free to file issues on Github!
https://github.com/Microsoft/WinObjC/
I want to know which is the best and most reliable method. i have looked on here for an answer but didn't come across any.
I Want to use multiple API'S in my project so please keep that in mind when answering. Any advice about the best way of doing this and most reliable method will really be appreciated. Thanks in advance!
Isit possible to download multiple SDK's into an iOS application through Xcode?
Pros of SDK:
Can be used offline
Most SDKs are small in file size
All of the functioning code is visible to you, the SDK developer can't keep many secrets
Cons of SDK:
Larger binary
More clutter in your Xcode project
Pros of API:
Smaller binary
Less 3rd party frameworks cluttering your Xcode project
Cons of API:
Can't be used offline
Tends to be a blackbox
App will need to be updated every time the API is updated
In terms of reliability, the SDK will always be functional assuming
It worked in the first place
It doesn't rely on an API in the background
You can integrate SDK using Cocoapods library.CocoaPods is a ruby gem that downloads all the third party libraries that you want for your project.
Getting a specific version of a pod is done by specifying the version number, and CocoaPods downloads that specific version for you saving you from searching through commits for it.
With CocoaPods, updating your dependancies is easily done with the pod update command.
CocoaPods also provides a central place where third party libraries can be found. This improves discoverability of open source libraries that you can use in your projects. You can use the search engine at cocoapods.org to search for pods.
EDIT: this question is outdated - TwitterKit is now available via CocoaPods
It seems to involve downloading an application, giving that application the path to my project, and adding one of their executables as a build phase.
It seems like that requires placing a lot of trust in Fabric...
Is there a good reason they're not providing the option to download TwitterKit in a more standard way, like a framework or a cocoapod?
Great question, the short answer is that we built the application to reduce friction when implementing any of the kits (TwitterKit, Crashlytics and MoPub).
Longer answer - there are various reasons for the Fabric application vs a "native" implementation. Currently the Fabric application provides a bunch of functionality that reduced friction for folks trying to implement any of the kits (i.e. Crashlytics, Twitter and MoPub). On the Crashlytics side we do a variety of things like take the dsym to replace the symbols in the crash logs with the appropriate methods names so crash reports are readable (also this makes it v.easy to provide a linkage between accounts, without the need for a key variable in the code). On the TwitterKit side it's fairly similar story, rather than take measures to get your keys/secrets from apps.twitter.com you can simply use the application that does some heavy lifting.
You can rest assured that the team isn't trying to do anything shady here. Feel free to reply here if you have any questions :-)
You are also free to download Twitter Kit as a CocoaPod: https://cocoapods.org/pods/TwitterKit
Just add the following to your Podfile:
pod 'TwitterKit`
Is there a way to use a dependency only in development? I don't want to ship the Reveal SDK :/
I'm searching for something similar to
#ifdef DEBUG
Can't find anything in the cocoapods docs.
Looks like it's scheduled for next release. See here:
https://github.com/CocoaPods/CocoaPods/issues/731
There is an issue on the CocoaPods github that is discussing the ability to dynamically link a pod based on the selected build configuration, but there is currently no release that supports this feature. According to the maintainers, the feature will be released in the next version of CocoaPods.