Removing a Cocoapod from the Specs Repo - ios

This post is in regards to two Cocoapods of which I am the owner of:
https://cocoapods.org/?q=id.me (There's only one cocoapod that shows up and I can't link to it because it's broken)
https://cocoapods.org/?q=idmeweb (There's only one cocoapods that shows up and I can't link to it because it's broken).
I need the first CocoaPod (which has already been deprecated), ID.me WebVerify to be completely removed as it's podspec points to a personal repo of mine, http://github.com/artsabintsev/Harpy/. The actual location it should have pointed to no longer exists, and my previous employer, ID.me, has asked me have it removed.
I need the second CocoaPod, https://cocoapods.org/pods/IDmeWebVerify, to work. Apparently, clicking on the link does nothing. My previous employer, ID.me, has asked me to figure out how to get it fixed.
Thank you for any and all assistance.

There are pod trunk x commands to deprecate and delete if you have admin access to them.

Related

How to update Overview/Changelog of cocoapods page

As I can see there are multiple complains already filed against not updating changelog/overview, this problem exists in their side, Cocoapods team is working on it but it is not fixed. (existing complains- https://github.com/CocoaPods/cocoadocs.org/issues/589) .
There is a webhook present to update the same but that is only for open-source projects but I own a private project, I am not able to change the overview page.
Admob has removed all the changelog and readme from their cocoapod and put a short version independent snippet(ref:-https://cocoapods.org/pods/Google-Mobile-Ads-SDK)
I am also trying to do the same, can anyone help me how to update the same?

How can I maintain an iOS Framework initially installed via CocoaPods but modified manually later on?

I'm currently working on a iOS (Swift) app for which I installed a few Frameworks via Cocoapods.
I have been facing a few issues with one of the frameworks and decided to tweak its code manually to run some tests and see if I could make things work.
I ended up figuring out a way to achieve what I wanted but I had to add a couple files in that framework as well as modify a few others.
This is the first time I do this and I'm almost certain this is no the best way to do things but I wanted to get some advices on how I can maintain that framework (that is behaving the way I want) in the future?
If I run "pod install" again, I suppose the framework and my changes will be overridden...
Any advice would be really appreciated.
Find the source repo (probably on GitHub) and fork it to your own account. Check out that repo and make your changes.
Optionally I would recommend making your adjustments to the code reusable so others can also use your tweaked version (make it configurable so they can turn the additional functionality on or off) and then submit a pull request back to the original repo.
If you don't want to do that you can point your Podfile directly to your customised repo using the following format:
pod 'Alamofire', :git => 'https://github.com/Alamofire/Alamofire.git'
Or you could look at creating your own CocoaPod (either by publishing to CocoaPods public specs repo or creating your own specs repo).

What is the official pod for G+ iOS SDK

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.

More FacebookSDK/Facebook.h issues - file not found

Alright, guys. I'm going freakin' crazy with this one. It is utterly ridiculous that the FacebookSDK causes so many issues. I know there are a couple questions on here regarding this issue, but they all seem to be outdated.
I pulled my Xcode project onto a new computer, and can't build it because I get the "FacebookSDK/FacebookSDK.h" file not found error. There are answers such as This one, but I've followed the steps in every single answer and haven't found one that works. I've just made a fresh pull from my working project from the original machine to the new one. I'll take some screenshots showing my current settings for various fields mentioned in other answers, and maybe I Just have something wonky that is interfering.
Here are the contents of the SDK that I just downloaded
Here are the contents of my Xcode project folder. There isn't anything else Facebook in here.
Here are the frameworks inside my Frameworks group and inside the Link Binary with Libraries section of Build Phases
There are a couple frameworks that are red, and that's OK for now. They were not in the repo, and are instead referenced from Documents or Downloads, and they played nice when I moved the files over and linked them. I just reset my repo to when I pulled it to make sure I didn't have anything from weird stuff I tried that prevents a proper solution from working.
Framework search paths. You can also see that my library search paths is empty. I labeled the stuff I wanted to hide, as it was identifying information
For some reason, my Documents for the new machine is already under the framework search paths. I did not add this myself.
Any ideas on what I can try? This is endlessly frustrating. I've wasted an entire day of development on trying to get Facebooks SDK re-integrated on a new machine.
I was also face the same problem every time I got the checkout for new version from svn.What I did was just removed the Facebook SDK and add again from the backup.It taken me out that time.Please try this might be it works for you.

SoundCloud iOS SDK fails to find all header files. libSoundCloudUI/CocoaSoundCloudUI

I have spent hours over the past week trying to figure out why SoundCloud suddenly stopped working in an app I'm working on. Figuring it might have been file-location related, I completely removed it and re-added the submodules. Then re-added after that didn't work. Then re-added. Then searched. Then nothing.
I've tried re-adding the SoundCloud submodules, and have followed the directions on the SoundCloud site to the T, and still, I get compiler error after error, warning after warning. I add the linker flags as stated, and include the needed frameworks and dependencies. I have absolutely no idea why I'm getting missing file errors.
Changing the Header Search Path (in either MY project file or libSoundCloudUI) just shifts what file can't be found, and when I somehow manage to get SoundCloud to compile with my program, anytime I commit my changes to my Git repository, the submodules are lost and the next person to open the project doesn't have the code, thus making me start over. Pointing the header search path directly to the source code doesn't work, even when it's recursive.
What could be happening? No matter what I do, specifically CocoaSoundCloudUI
Some of the errors I've been getting:
Use of undeclared identifier: 'kTermsofService' (This has a few other keys that aren't being found)
Header file not found: <insert random file include in headers and in source folder>
If my app didn't need SoundCloud support I would have dropped it already. This has been such a nightmare - any help would make my life a lot easier.
Hi Sean Michael Dorian,
indeed, we have updated CocoaSoundCloudAPI and CocoaSoundCloudUI lately and according to your error message you have not updated both repos, i.e. you need to run
git submodule update --init --recursive.
If you have issues w/ submodules in general I recommend you switching to CocoaPods it turns the management of your library dependencies into a no-brainer.
We also provide a Demo Xcode project to check out such a setup.
This should help you resolving the issues let me know if you are missing anything there.

Resources