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
I'm receiving an issue with a previous release on Google...
Andrew Fletcher
The "keystore password was incorrect" error in keytool indicates that the...
Andrew Fletcher
How to generate a new private key and submit it to Google Play for signing your...
Andrew Fletcher
Issues with sign in key... When attempting to upload a APK package, I'm getting...
Andrew Fletcher
Setting up the admin password.   Process: 1. Edit jetty.xml To begin you are going to edit the file “server/etc/jetty.xml”.  However, if you aren't sure of the location of jetty.xml, run the command find / -name jetty.xml -type fFor me, the output was /opt/solr-8.11.1/server/etc/jetty.xmlEdit the file jetty.xml, by adding it before the Configure tag ends <Callname="addBean"> <Arg> <New class="org.eclipse.jetty.security.HashLoginService"> <Set...
Andrew Fletcher
In this article I'll walk through the steps I went through to install Solr on...
Andrew Fletcher
Looking to install Solr on your server?  Not sure if it worth the...
Andrew Fletcher
Getting Started with Cocoapods Installation Built with Ruby, Cocopods is...
Andrew Fletcher
Having Drupal Solr Search APi running, I thought adding synonyms to the mix...
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....