How to run CocoaPods on Apple Silicon (M1)

IosMacosFlutterCocoapodsApple Silicon

Ios Problem Overview


I have a Flutter project that I'm trying to run on iOS. It runs normally on my Intel-based Mac, but on my new Apple Silicon-based M1 Mac it fails to install pods.

LoadError - dlsym(0x7f8926035eb0, Init_ffi_c): symbol not found - /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi_c.bundle
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi.rb:6:in `rescue in <top (required)>'
/Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/lib/ffi.rb:3:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Library/Ruby/Gems/2.6.0/gems/ethon-0.12.0/lib/ethon.rb:2:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Library/Ruby/Gems/2.6.0/gems/typhoeus-1.4.0/lib/typhoeus.rb:2:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/sources_manager.rb:74:in `cdn_url?'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/sources_manager.rb:36:in `create_source_with_url'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/sources_manager.rb:21:in `find_or_create_source_with_url'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/analyzer.rb:178:in `block in sources'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/analyzer.rb:177:in `map'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/analyzer.rb:177:in `sources'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/analyzer.rb:1073:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/analyzer.rb:1072:in `resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer/analyzer.rb:124:in `analyze'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer.rb:414:in `analyze'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer.rb:239:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer.rb:238:in `resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/installer.rb:160:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.10.0/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

Based on a Github workaround, I tried to run Terminal using rosetta, but the issue remains the same: https://github.com/CocoaPods/CocoaPods/issues/9907#issuecomment-655870749

Realising it's still early for Macs with Apple Silicon. Is there a way to make this work for the time being?

Ios Solutions


Solution 1 - Ios

2022 May Update

If you can use Homebrew to manage cocoapods.

# Uninstall the local cocoapods gem
sudo gem uninstall cocoapods

# Reinstall cocoapods via Homebrew
brew install cocoapods

2021 Solution

# STEP 1: Install ffi
sudo arch -x86_64 gem install ffi

# STEP 2: Re-install dependencies
arch -x86_64 pod install

Additional Information

#1 For anyone seeing the arch: posix_spawnp: gem: Bad CPU type in executable error, you must first install Rosetta. Thanks, @Jack Dewhurst

#2 If you run pod commands pretty often, setting up an alias in .zshrc or .bash_profile might be handy. Thanks, @theMoonlitKnight for the suggestion.

alias pod='arch -x86_64 pod'

Solution 2 - Ios

EDIT: I recently disabled Rosetta, and Cocoapods runs just fine with the addition of the ffi gem.

For anyone else struggling with this issue, I just found a way to solve it. In addition to running terminal in Rosetta:

  1. Right-click on Terminal in Finder
  2. Get Info
  3. Open with Rosetta

I installed a gem that seems to be related to the symbol not found in the error:

sudo gem install ffi

After doing this, cocoapods runs as expected.

Solution 3 - Ios

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.

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 https://github.com/ffi/ffi/blob/dfae59e293974efaa7b4d414e5116d7a2187a06e/lib/ffi/platform.rb#L61 and https://github.com/ffi/ffi/blob/e3f2cf9b82055709ddbeecbf77810f43438c4b64/spec/ffi/fixtures/compile.rb#L11), we end up with OP’s error message.

The solution is, therefore, to get a version of Ruby built specifically for arm64 by using either Homebrew, rbenv or RVM.

For Homebrew:

  • Execute brew install ruby
  • Add export PATH=/opt/homebrew/opt/ruby/bin:/opt/homebrew/lib/ruby/gems/3.0.0/bin:$PATH to your .zshrc (you can find your Homebrew installation directory with $(brew --prefix) if needed)
  • Execute source ~/.zshrc or restart your shell
  • Make sure you are using the correct ruby binary by executing which ruby (should be $(brew --prefix)/opt/ruby/bin/ruby)
  • Install CocoaPods with sudo gem install cocoapods
  • Make sure you are using the correct pod binary by executing which pod (should be $(brew --prefix)/lib/ruby/gems/3.0.0/bin/pod)
  • Make sure ethon is version 0.13.0 or more with gem info ethon, otherwise run sudo gem install ethon
  • Run pod install
Ruby won't come with future macOS versions by default

Moreover, it should be noted that ruby is still included in macOS only « for compatibility with legacy software », as evidenced by running irb -v, so this is probably a good opportunity to install your own version anyway:

> WARNING: This version of ruby is included in macOS for compatibility > with legacy software. In future versions of macOS the ruby runtime > will not be available by default and may require you to install an > additional package. > > irb 1.0.0 (2018-12-18)

Sources:

Solution 4 - Ios

To install completely cocoapods on Mac with M1 chip (Apple Silicon), please follow these steps:

  1. Duplicate the Terminal application in the Utilities folder.
  2. Right-click on the app and choose to Get Info.
  3. Rename the other version of the app as you like.
  4. Check the option "open with Rosetta".
  5. Install Cocoapods with the command "sudo gem install cocoapods"
  6. Type the command line "gem install ffi" to fix the ffi bundle problem. Now you can do a "pod install" without a problem.

Source : iPhoneSoft

Solution 5 - Ios

Simplest way I found :

sudo gem uninstall cocoapods

brew install cocoapods

Solution 6 - Ios

An alternative to running Terminal in Rosetta 2 is to set the architecture with arch -x86_64, as in the following:

arch -x86_64 sudo gem install cocoapods -n /usr/local/bin

To give credit where it is due, I found this solution here

MacPorts bug tracker, issue #61545, comment 7

Solution 7 - Ios

  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

Solution 8 - Ios

There is a much "better/easier?" way by way of using homebrew now that waters have settled, if you have homebrew install just run

brew install cocoapods

this will install ruby and libyaml as preconditions, so far this is the most straightforward way (and the one, most probably, to be recommended moving forward).

Solution 9 - Ios

UPDATE 28th MARCH

1- arch -x86_64 sudo gem install cocoapods -n /usr/local/bin

2- arch -x86_64 sudo gem install ffi

3- pod install

No need to duplicate or Open with Rosetta

Solution 10 - Ios

Working in Sept 2021, Mac M1

I just want to add to Medhi's answer, to do a "pod repo update" within the same terminal inside the iOS folder, because that was critically fixing the error for me.

Here's the complete To-do-list:

  1. Duplicate the Terminal application in the Utilities folder.

  2. Right click on the app and choose "Get Info".

  3. Rename the other version of the app as you like.

  4. Check the option "open with Rosetta".

  5. Install Cocoapods with the command sudo gem install cocoapods

  6. Type the command line sudo gem install ffi to fix the ffi bundle problem.

  7. Go to the iOS folder of your app in the same terminal

  8. Do pod repo update

  9. Now you can do a pod install without a problem.

Solution 11 - Ios

Basically tried all solutions listed here.

$ arch -arm64 brew install cocoapods

finally did it for me.

Before doing that, be sure to have homebrew correctly installed with /opt/homebrew being the prefix. This article provides pretty good instructions on this.

Edit: Another option is to remove all your flutter and dart files and just use homebrew for the complete installation process as shown here. This also worked for me on M1 Pro.

Solution 12 - Ios

Install cocoapods

sudo arch -x86_64 gem install ffi

Install pod file

arch -x86_64 pod install

Update pod

arch -x86_64 pod update

Solution 13 - Ios

Try $ sudo gem install ffi. It works fine for me.

Solution 14 - Ios

I had the same issue and this is what helped me. Open the terminal and type the below command :

arch -x86_64 sudo gem install ffi

Solution 15 - Ios

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

Solution 16 - Ios

If your case is that you've updated your project and already have ffi installed, you will need to run this:

arch -x86_64 pod install --repo-update

Solution 17 - Ios

✅ The following solution work for me on my Apple M1 machine.

I've spent over a week searching for a solution to install CocoaPods successfully on a M1 machine. You may see if my method works for you or not. 

The solution requires the Terminal.app to be running in "Rosetta" mode.

But it does not required the Terminal to be running in x86.

[Environment]

Mac mini (M1, 2020) / macOS Big Sur (Version 11.5.2) / Xcode Version 13.0 (13A233)


Terminal + Rosetta

(Rosetta is required on CocoaPods installation)

To run the terminal.app in "Rosetta" mode,

Right click the Terminal.app > Select "Get Info" > Make sure "Open using Rosetta" is checked.

Image showing a checkbox with item


Steps

(1) Run the following lines for updating gem.

Make sure you gem version is up-to-date before executing any commands following. The update is introduced by this article on Medium.

sudo gem update -n /usr/local/bin --system

sudo gem install  -n /usr/local/bin cocoapods --pre

(2) Execute the commands using the "sudo" command.

sudo gem install

(3) Install an older version of CocoaPods

As the latest version (1.10.0) cannot be installed for my case. I've tried installing an older version. The line execute successfully without any error messages.

You may check the thread on Apple's forum.

sudo gem install -n /usr/local/bin cocoapods -v 1.8.4

Solutions on Error

Then, the compiler may bring you some error, like "active developer path do not exist". This error would shown if you've installed a beta version of Xcode on your machine.

You would need run following lines for the compiler to switch to a new active path, pointing to the new Xcode app.

sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer

If your Xcode refuses to switch, you may check out this thread on Apple's forum to see if it helps.


Final Step ⬇️

(1) Uncheck "Open using Rosetta"

Then, may go back to the "info" panel and uncheck "Open using Rosetta", but unchecking Rosetta is optional. You may keep the box checked if it is needed.

(2) Run CocoaPods commands as usual

After that, you can back to the project directory and run commands pod init to initiate the CocoaPods for your project as usual

Steps for a normal CocoaPods build:

  1. pod init
  2. open Podfile
  3. edit Podfile (for specifying pods)
  4. pod install
  5. The .xcworkspace is ready to be opened in Xcode.

Use sudo xcodebuild -license if you've faced an error (regarding to Xcode registration).

Solution 18 - Ios

I've been having the same issue. I did find that the cocoa pods UI app seems to work as expected.

Solution 19 - Ios

this is what i got when trying to instal ffi in native terminal:

Fetching ffi-1.13.1.gem
Building native extensions. This could take a while...
ERROR:  Error installing ffi:
    ERROR: Failed to build gem native extension.

    current directory: /Library/Ruby/Gems/2.6.0/gems/ffi-1.13.1/ext/ffi_c

switching to Rosetta enabled terminal, installing "gem install cocoapods" fails on

You don't have write permissions for the /usr/bin directory.

but then installation of ffi was successful...

Finally solved it with

sudo gem install cocoapods -n /usr/local/bin

Solution 20 - Ios

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

Solution 21 - Ios

This is how I solved my problem in M1. Someone might be helped.

From System preference. User & group. Set login shell as

   /bin/bash 

Then close the terminal and reopen it.run this command

sudo gem install -n /usr/local/bin cocoapods -v 1.8.4

Hopefully, this will works.

Solution 22 - Ios

Install pod in project without using rosetta terminal just follow below steps

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

Solution 23 - Ios

Pod Not installing on M1 Chip MAC ??? No worries

run below three commands : -

pod deintegrate

sudo arch -x86_64 gem install ffi

arch -x86_64 pod install

it works !!

Solution 24 - Ios

Mac M1 MacOS BigSur solution:

brew cleanup -d -v    
brew install cocoapods
brew link --overwrite cocoapods

Solution 25 - Ios

For updating pods, maybe someone will help:

After installing ffi:

sudo arch -x86_64 gem install ffi

Update dependencies

arch -x86_64 pod update

Solution 26 - Ios

I did get this problem after new dependencies (Firebase) where added to the repo. Was then able to do the sudo arch -x86_64 gem install ffi, but other problems remained after it.

My fix was: re-cloning the repo and running it again.

Setup: Xcode 12.4 Mac M1 react-native 63.4

Solution 27 - Ios

I have a twist to this answer:

  1. run
sudo gem install ffi
  1. the twist: I restarted my machine and then it worked.

Solution 28 - Ios

I had the same problem with my new MacBook Air M1 just because m1 has a different architecture we should install packages with Rosetta Translation Environment.

You can solve most compatibilities by using rosetta.

STEPS TO SOLVE:

  1. Open finder/applications
  2. Duplicate your terminal
  3. Right-click the new terminal and check the checkbox [x] open using

and then install packages with this terminal enter image description here

Solution 29 - Ios

the solution for me was to add arch -x86_64 at the begining of the create command

Solution 30 - Ios

If you Are using M1 chip system then use-

go to application folder-

select terminal open with rosseta- then run cmd-

sudo arch -x86_64 gem install ffi

Then

arch -x86_64 pod install

Solution 31 - Ios

This is what worked for me, trying to build app on Mac M1

first go to your applications folder and

select terminal app -> get info -> select run with rosseta

// if you are trying to build the app through xcode Repeat the above steps for xcode app

Note: Make sure your terminal and code are closed while doing so.

Now run your terminal switch to your project_folder/ios

Run below-shown commands

sudo gem install cocoapods

sudo gem install ffi

sudo arch -x86_64 gem install ffi

Solution 32 - Ios

All of the above solutions are valid, just wanted to post that with home brew and cocoapods supports native Apple Silicon chips you can run the command without prefixing arch -x86_64

so, sudo gem install ffi will do the job.

Solution 33 - Ios

without Rosetta you can do like this

  1. Ensure OS is updated to macOS Big Sur 11.3.1
  2. /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
  3. brew install cocoapods

Solution 34 - Ios

If you are on an older project that needs to be ported over don't forget to update the project.pbxproj files in your Runner.xcodeproj and Pods.xcodeproj.

The IPHONEOS_DEPLOYMENT_TARGET probably is still pointed towards 8.0

Update all occurrences as follows:

IPHONEOS_DEPLOYMENT_TARGET = 9.0;

Solution 35 - Ios

For Final Run Mac 1 Silicon 0.65 (any version)

Npx react-native init Nitin2

Then change the pod file

Go to

Cd iOS

Open pod file

Add

platform :ios, '12.1'

use_flipper!() post_install do |installer| react_native_post_install(installer) installer.pods_project.build_configurations.each do |config| config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64" end end

And bridge header by adding the new swift file and after addition of bridge header please delete the swift file otherwise swift file may generate error.

Pod File

For Creating the Swift File.

Go to project nitin2 -> Nitin2 (sub project) and right click on it Click New File Select swift file -> next Then select the nitin2 directory in the iOS folder Leave the file name same Click checkbox nitin2 in the target Click create Now the it will ask to create the bridging header.h Yes create the file And now go to

Go to project nitin2 -> Nitin2 (sub project) See the file.swift and delete it.

xcode add the bridge header arm64

Now go to Xcode -> target Nitin2 -> build setting In ARCHITECTURES CLICK EXCLUDED ARCHITECTURES AND ADD THE arm64

Now Remove the build folder from Xcode product menu

Now do the things through terminal

Cd go to iOS directory

pod cache clean --all

yarn cache clean

rm -rf ~/Library/Developer/Xcode/DerivedData/*

open nitin2.xcworkspace

rm -rf Pods Podfile.lock

pod deintegrate && pod setup && pod install

code /Users/nitin/D1/www/projects//ios/Pods/../../node_modules/react-native/React/FBReactNativeSpec/../../scripts/generate-specs.sh

Add export PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin

Then run the iOS npx react-native run-ios

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJacobo KoenigView Question on Stackoverflow
Solution 1 - IosX.CreatesView Answer on Stackoverflow
Solution 2 - IosJacobo KoenigView Answer on Stackoverflow
Solution 3 - IosValentin BriandView Answer on Stackoverflow
Solution 4 - IosMedhiView Answer on Stackoverflow
Solution 5 - IospravchukView Answer on Stackoverflow
Solution 6 - IospfurbacherView Answer on Stackoverflow
Solution 7 - IosHarshit JainView Answer on Stackoverflow
Solution 8 - IossamiqView Answer on Stackoverflow
Solution 9 - IosJadView Answer on Stackoverflow
Solution 10 - IosusernameView Answer on Stackoverflow
Solution 11 - IosMatteoView Answer on Stackoverflow
Solution 12 - IosSureshkumar LinganathanView Answer on Stackoverflow
Solution 13 - IosKevinView Answer on Stackoverflow
Solution 14 - IosABMView Answer on Stackoverflow
Solution 15 - IosAhmed KamalView Answer on Stackoverflow
Solution 16 - IosRafael AffonsoView Answer on Stackoverflow
Solution 17 - Ios21.kawView Answer on Stackoverflow
Solution 18 - IosStropdaleView Answer on Stackoverflow
Solution 19 - IosAn ChinView Answer on Stackoverflow
Solution 20 - IosWaSderinoView Answer on Stackoverflow
Solution 21 - IosShourob DattaView Answer on Stackoverflow
Solution 22 - Iosuser7393040View Answer on Stackoverflow
Solution 23 - IosGovind WadhwaView Answer on Stackoverflow
Solution 24 - IosMichał Dobi DobrzańskiView Answer on Stackoverflow
Solution 25 - IospajtimidView Answer on Stackoverflow
Solution 26 - IosPatrik Rikama-HinnenbergView Answer on Stackoverflow
Solution 27 - IosScottyBladesView Answer on Stackoverflow
Solution 28 - IosAbdug'affor AbdurahimovView Answer on Stackoverflow
Solution 29 - IosBlueView Answer on Stackoverflow
Solution 30 - IosRohit NishadView Answer on Stackoverflow
Solution 31 - IosVicky SalunkheView Answer on Stackoverflow
Solution 32 - IosHamza JadidView Answer on Stackoverflow
Solution 33 - IosParesh MangukiyaView Answer on Stackoverflow
Solution 34 - IosDavid TengView Answer on Stackoverflow
Solution 35 - IosNitin BindalView Answer on Stackoverflow