cocoapods installation stuck on "Updating local specs repositories" - xcode

Any help please I have been waiting so long for this and it didn't show me any improvement.Still stucking at Updating local specs repositories
Actually i was trying to update pod files of library that I use on my xcode.I close it yesterday because it takes too long.And today i run again,doing control + c and run pod install again.
It didn't work,stucking at Updating local specs repositories
When I open my Xcode,many errors occur because of pod issue..
Please I need help!

There's an known error with http://blog.cocoapods.org/Repairing-Our-Broken-Specs-Repository/
You can try to fix it by doing:
pod repo remove master
pod setup
pod install

For me it already happened a few times, always after cocoapods failing to contact github on a previous run if I'm not mistaken.
I solved by simply deleting the contents of ~/.cocoapods/repos. and running the pods again

It looks like specs repos will be updated by default when you run pod update. Including --no-repo-update in the pod update command solved the issue for me
pod update POD_NAME --no-repo-update
Reference:
https://github.com/CocoaPods/CocoaPods/issues/4218#issuecomment-141678644

Also on these days some users sugest update Ruby via homebrew
Check this issue:
https://github.com/CocoaPods/CocoaPods/issues/7447

Related

Cant build ios app after installing Firebase

I've followed all the proper steps to installing cocoapods and Firebase to my app, but for some reason, I keep getting the same Shell Script Invocation Error:
/Users/Guest/Library/Developer/Xcode/DerivedData/NewApp-eszjuaizunqxaofbuqgmicbnvqkh/Build/Products/Debug-iphonesimulator/NewApp.app/Frameworks/GoogleToolboxForMac.framework: No such file or directory
For this reason I cannot build and run my app. I've searched and followed all suggestions I could find, but nothing has worked. So far I have updated my pods, deleted Derived Data, and deleted everything from the pods to my project and restarted using my backup file.
Can someone pleeease help?
This is a pretty common that happens a lot when using Firebase with Xcode! I assume that you are using CocoaPods to download the correct frameworks. A could of things to try:
1. In Xcode go to the top bar and go to: Product -> Clean
2. Just restart Xcode! (Make sure that all Xcode related tasks aren't running) Command + Q then make sure that its no longer in your dock running
3. Go into terminal and run these commands to redownload your pod files
pod deintegrate
pod clean
pod install
If these don't work just continue trying these steps and it will probably hopefully work
Deleting the file and starting from scratch solved my issue

Heroku CLI hangs on Windows 10

I use Heroku CLI on Windows 10. The first day after installing it works just fine, but on the next day (or so) it just hangs after launch:
C:\Users\{User}>heroku
and that's all. No output to console, no logs (no error.log). It lasts forever (not 120 sec like here: Heroku CLI Unresponsive)
I reinstalled CLI on 10.10.2017. Today is 14.10, my folder contains the following files:
folder view before cleaning
The autoupdate.log contains:
[2017-10-10T13:36:14+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from
heroku-cli: Updating CLI... already on latest version: 6.14.34-1fcf80e
heroku-cli: Updating plugins... done
[2017-10-11T22:36:40+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from logs
heroku-cli: Updating CLI... already on latest version: 6.14.34-1fcf80e
heroku-cli: Updating plugins... Waiting for all commands to finish
heroku-cli: Updating plugins... done
[2017-10-14T01:13:34+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from logs
heroku-cli: Updating CLI... already on latest version: 6.14.34-1fcf80e
heroku-cli: Updating plugins... Waiting for all commands to finish
What have I tried:
uninstall and install again - this one works, but I don`t want to do
this every day
running as administrator
waiting all night long
using different commands (heroku --version, heroku update etc)
delete folder ..\AppData\Local\heroku
After deleting the folder and running command 'heroku update' the following files & folders were created, but console still hangs:
folder view after cleaning
The autoupdate.log consists now of 1 line:
[2017-10-14T19:39:02+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from update
I waited for an hour since and now writing this question here. Has anyone faced such an issue? What can be done?
Update
Finally I made it work after a few days by reinstalling CLI several times and deleting the autoupdate files, but cannot say precisely which of my actions had true effect. If you face the same issue you can start with the Malik`s answer.
I encountered the same problem when I run $ heroku login on GitBash for Windows.
I tried the accepted answer above but to no avail. What solved it was just to use Windows Command Prompt instead of GitBash and all problems were solved.
I'm just adding this answer here in case someone has done the same thing like I did.
Using GitCMD instead of GitBash solved the problem for me.
I had the same issue and i followed these steps to fix it.
Go to heroku AppData directory. (windows run %LOCALAPPDATA%\heroku)
You should see 2 files named as autoupdate and a directory named as update.lock.
Delete these 2 files and the directory.
Open a new cmd window.
Try running the heroku cmd again. Now it should work for you.
I use following version
heroku-cli/6.14.36 , (windows-x64) , node-v8.9.0.
Relevant github issue thread
I got the same symptom because I was behind a proxy but did not set the proxy env vars.
export HTTP_PROXY=http://proxy.server.com:portnumber
export HTTPS_PROXY=https://proxy.server.com:portnumber
heroku login
Usin CMD git for heroku login. I had to do the other steps using the bash and all was perfect.

MODULE_NOT_FOUND in heroku pg:backups

I've got problem with heroku pg:backups capture --app myapp command.
Heroku CLI submits usage information back to Heroku. If you would like to disable this, set `skip_analytics: true` in /home/ubuntu/.heroku/config.json
heroku-cli: Updating to 4.99.0-e5f5ef4... done
heroku-cli: Updating CLI...heroku-cli: Updating to 5.11.8-f58f4fa... done
Starting backup of postgresql-spherical-5948... done
Use Ctrl-C at any time to stop monitoring progress; the backup will continue running.
Use heroku pg:backups:info to check progress.
Stop a running backup with heroku pg:backups:cancel.
Backing up DATABASE to b598... pending
Backing up DATABASE to b598... !
▸ MODULE_NOT_FOUND: Cannot find module 'bytes'
Does anybody have similar problem? This command is launched with deploy on CircleCI.
I started running into the same problem yesterday and was finally able to come up with a solution that is working for me.
For starters, it looks like bytes is a dependency of heroku-pg, which is the part of Heroku CLI that is being used for the backups command. It seems like the dependency is not being included or installed with the version of heroku-cli that is being used to run the backup command.
I tried CircleCI’s “Rebuild with SSH” to troubleshoot the issue, and encountered similar error messages when attempting the backup command there. While trying to reinstall heroku-cli using npm, I found that the npm and node versions were way behind what heroku-cli wanted, so maybe that is part of the problem? Anyway, reinstalling with npm only produced an even more broken Heroku CLI.
Finally I checked the build environment and it was set to Ubuntu 12.04 (Precise) which probably explains the way out of date npm/node packages. I changed it to Ubuntu 14.04 (Trusty) and pushed a new commit to CircleCI (A rebuild alone is not sufficient to change OS versions) and was able to successfully run the backup command that had been failing!
Solution: Set CircleCI build environment to Ubuntu 14.04

Installing sensu, sensu-dashboard does not install

I am installing a sensu server inside a docker container running ubuntu 14.04 but when I install it for some reason it does not install the sensu-dashboard.
When I run the following command to set up the defaults I get a file does not exist error
> Command: update-rc.d sensu-dashboard defaults
Error: update-rc.d: /etc/init.d/sensu-dashboard: file does not exist
I have searched for the file but does not seem to be installed anywhere.
Has anyone else had this problem before when installing sensu or know how to fix it?
Thank you
The default Dashboard was removed on July 28th so you missed it by a day!! :( You now have to use a different dashboard. Uchiwa is a great choice and is under very heavy development, so I am sure it will continue to become more feature rich.
link to uchiwa's github page
The default Dashboard was removed that is true but if want to use sensu-dashboard then go for Sensu-Enterprise.
Here is the link: http://sensuapp.org/enterprise

cocoapods: pod update and pod install takes forever

I try to update my podfile using the command pod update but it takes forever.
I did also all the steps according to this question cocoapods - 'pod install' takes forever but nothing changed.
Using the command pod update --verbose i see that it stops here: Updating spec repo master
$ /usr/bin/git pull --ff-only
Any suggestion?
CocoaPods has to download a repository of all podspecs to do its work. It seems like it's that pull operation that's taking a long time. I'm not aware of any way to accelerate that process.
However subsequent pod operations will be much faster until new commits are available in the master spec repo. So if you have several update or install operations, doing them together can save you some time.
There is a rate limiting on git servers and that seems to slow down the process.
Like Fabian said there is no valid solution at the moment but splitting the update to individual pods. There is an explanation at the CocoaPods blog Master spec-repo rate limiting post‑mortem, it seems we need to wait for 1.0.0.beta.7 before they fix the issue.
Meanwhile, this Git Issue on the topic recommends to run convert your Podspecs to be a full copy instead of a shallow clone, by running:
cd ~/.cocoapods/repos/master && git fetch --depth=2147483647
you can run
pod install --verbose
to see what's going on behind the scenes.. at least you'll know where it's stuck at (it could be a git clone operation that's taking too long because of your slow network etc)
check this for more clarified answer
https://stackoverflow.com/a/25658514/1894306

Resources