Login

For updating pods, maybe someone will help:

After installing ffi:

sudo arch -x86_64 gem install ffi

Update dependencies

arch -x86_64 pod update

I have a twist to this answer:

1. run

```
sudo gem install ffi
```

2. **the twist**: *I restarted my machine* and then it worked.

Install cocoapods

sudo arch -x86_64 gem install ffi

Install pod file

arch -x86_64 pod install

Update pod

arch -x86_64 pod update

As of version `1.10.1` Jan 7, 2021, CocoaPods is now supporting the new M1 chip.

1. ***Execute*** below to ***install*** the required ***ffi*** :

`sudo arch -x86_64 gem install ffi`

2. Instead of `pod install` use :

`arch -x86_64 pod install`

**Install pod in project without using rosetta terminal**
just follow below steps
- sudo arch -x86_64 gem install ffi
- arch -x86_64 pod install

**IN MAC M1**, for anyone using KMM (Kotlin Multiplatform Mobile), but it may work for other, finding that it does not create files on the `.xcworkspace` for the iOS APP, when using CocoaPods as dependency manager, first install CocoaPods by typing

sudo gem install cocoapods

than navigate to your project folder, now on the iOS folder and type

sudo arch -x86_64 gem install ffi
arch -x86_64 pod install

Now you should find all the files in iOS workspace.
If you have problems with

/Users/$name/$directory/$projectName/$iosFolderName/$iosAppName.xcodeproj
The linked and embedded framework 'Pods_iosApp.framework' is missing one or more architectures required by this target: x86_64.

You need to add **arm64** to xCode, click on the project folder -> **Build Settings** -> and search for **Excluded Architectures** and add **arm64**

### TL;DR:
- Install your own version of Ruby with Homebrew / rbenv / RVM (e.g. `brew install ruby`)
- Add it and the gems binaries to your `PATH` and make sure the new version is used with `which ruby` (should be `/opt/homebrew/opt/ruby/bin/ruby` instead of `/usr/bin/ruby` if installed with Homebrew)
- Install CocoaPods with `sudo gem install cocoapods` (make sure `ethon` is at least version 0.13.0)
- Run `pod install`

### Detailed answer:
All answers suggesting using Rosetta / `arch -x86_64` are workarounds and not quite solving the real issue that comes from the way RbConfig and the universal binaries work.

```rb
require 'rbconfig'

OSVERSION = RbConfig::CONFIG['host_os']
ARCH = RbConfig::CONFIG['arch']
HOSTCPU = RbConfig::CONFIG['host_cpu']
BUILDCPU = RbConfig::CONFIG['build_cpu']
TARGETCPU = RbConfig::CONFIG['target_cpu']

puts "OS: #{OSVERSION}"
puts "Arch: #{ARCH}"
puts "Host CPU: #{HOSTCPU}"
puts "Build CPU: #{BUILDCPU}"
puts "Target CPU: #{TARGETCPU}"
```

If you call `ruby` on a file containing this code with the universal binary shipped with macOS, you will get the following result on an M1 Mac:
```
OS: darwin20
Arch: universal-darwin20
Host CPU: x86_64
Build CPU: x86_64
Target CPU: universal
```
As you can see, RbConfig was compiled for a « universal » CPU but built with an x86 CPU, and the `rbconfig.rb` file that was generated (see `/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/universal-darwin20/rbconfig.rb`) consequently uses invalid information for the host CPU.

As `ffi` uses information from RbConfig (see