Skip to main content
11
results
Andrew Fletcher
The error you're encountering indicates an issue with the ffi gem during the CocoaPods update. The error message suggests trying to run the gem pristine command to fix it. Using terminal - run the following command: gem pristine ffi --version 1.16.3This command will attempt to restore the ffi gem to its pristine state, resolving any issues with its extensions. After running this command, try running pod update again pod updateIf you encounter any permission issues, you might need to use...
Andrew Fletcher
In Vim, following is an outline of the vi(m) functions you can utilise whilst in...
Andrew Fletcher
To completely remove Microsoft Remote Desktop from OSX you need to perform the...
Andrew Fletcher
The cache system in Drupal 9 delivers the API with the elements required for...
Andrew Fletcher
Installing Varnish to increase the speed of the page load. Install varnish using...
Andrew Fletcher
Clear DNS Cache The DNS (Domain Name Service) cache on your Mac helps browsers locate and connect to web addresses quickly. If your browser Safari or Chrome still fails to load websites, this can be the result of an obsolete DNS cache may be causing the issue. In this instance you want to focus clearing the cache.  Using Terminal or iTerm2 enter the following command: sudo killall -HUP mDNSResponder 
Andrew Fletcher
Getting Started with Cocoapods Installation Built with Ruby, Cocopods is...
Andrew Fletcher
Regular expressions (regex) are extremely useful in extracting information from...
Andrew Fletcher
Whilst updating nodejs and npm on a Centos 6 or 7 server running Apache, I...
Andrew Fletcher
Recently I had an error with a domain smtp server not recognising port 587....
Andrew Fletcher
Today while in Terminal, I ran a regular script pod update.  However, this time I received the following error [!] CDN: trunk URL couldn't be downloaded: https://raw.githubusercontent.com/CocoaPods/Specs/master/Specs/d/a/2/Alamofire/5.1.0/Alamofire.podspec.json Response: Timeout was reachedI read on GitHub that it could be a cache issue, so I ran: sudo rm -rf ~/.cocoapods/repoNo change. Instead of attempting a pod update, I changed the command to pod install.  Worked a treat....