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
Installing PHP on OSX and it installed PHP 8.2.x.  However, for my...
Andrew Fletcher
Regular commands for brew   Brew update This updates Homebrew itself....
Andrew Fletcher
Find by file name To perform a find command in terminal use find / -name...
Andrew Fletcher
 ERROR Error: Uncaught (in promise): TypeError: undefined is not an object...
Andrew Fletcher
Working through an app project I inherited using Ionic, Angular and ngx-leaflet to name a few elements... I had a problem where the map shows only all map tiles when navigating via my app in the Xcode simulator.  The simulator screen would show just a small tile and the rest of the area where the map should be visible stays in gray color. Image   Versions plugin /...
Andrew Fletcher
The issue Text through the app is being rendered as <p>Depletion...
Andrew Fletcher
In terminal I ran a regular command - compose update.  Something I've...
Andrew Fletcher
Getting Started with Cocoapods Installation Built with Ruby, Cocopods is...
Andrew Fletcher
Step 1: Install Homebrew Homebrew is the missing package manager for macOS. As...
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....