[tools] Remove ethon override (#23543)

Update CocoaPods to 1.12.1 (#22238)

Co-authored-by: Tomasz Sapeta <[email protected]>

[fastlane] Bump version

[gem] Update json gem to work well on M1

Update CocoaPods to 1.11.2

Update fastlane

Update CocoaPods to 1.11.0 (#14378)

[ios] Update CocoaPods to 1.10.2 (#14037)

[gemfile] Update ethon to avoid segmentation fault crashes on M1

[gemfile] Update json gem

[ios] Upgrade CocoaPods to 1.10.1

[repo] Upgrade Ruby dependencies (#11044)

# Why

I noticed Ruby got recently upgraded — https://github.com/expo/expo/commit/32491227db0716485556d996dd390f76d0963599. So I installed the recommended

[repo] Upgrade Ruby dependencies (#11044)

# Why

I noticed Ruby got recently upgraded — https://github.com/expo/expo/commit/32491227db0716485556d996dd390f76d0963599. So I installed the recommended version. Then I went to see if pod installation still works with new Ruby and noticed the installed CP version prints many unnecessary warnings like
```
/Users/sjchmiela/Applications/expo/.direnv/ruby/gems/cocoapods-core-1.9.3/lib/cocoapods-core/cdn_source.rb:342: warning: URI.escape is obsolete
```
Then I checked out CocoaPods releases, noticed there's one we could upgrade to, upgraded and here we are.

# How

Updated versions in `Gemfile` to latest, ran `bundle install` and then `pod install` in both `ios` directories in the repository.

# Test Plan

I have verified Expo Client compiles and runs.

show more ...

[repo] update fastlane to 2.159.0

Update CocoaPods to 1.9.3

Podfile locks have already been generated with this version

Update fastlane to 2.149.1

[repo] Upgrade CocoaPods and Fastlane (#8560)

# Why

When running `git pull` I noticed a strangely long output mentioning a lot of new `.xcconfig`s so I went to see when and why they were added. T

[repo] Upgrade CocoaPods and Fastlane (#8560)

# Why

When running `git pull` I noticed a strangely long output mentioning a lot of new `.xcconfig`s so I went to see when and why they were added. The commit adding them was [Publish expo-permissions, expo-notifications](https://github.com/expo/expo/commit/264a8722e01eb91cf1ec20eb5bdd09dd26fb829d). This does not sound like a commit that willingly upgrades CocoaPods used throughout the repository (which it did), so I decided to:
- fix the long-standing problem of `pod` being used not-from-the-bundle
- upgrade CocoaPods and Fastlane while I'm at it

# How

- updated version requirement for CocoaPods to `~> 1.9.1`
- had to run `gem install bundler:2.1.4` even though I thought I've already run this command some time before
- ran `bundle install` to install new CocoaPods
- updated version requirement for Fastlane to `~> 2.148.0`
- ran `bundle install` to install new CocoaPods
- added `pod` and `fastlane` executables to the `bin` directory that are similar to `lock` executable—they are like an alias that makes `pod <X>` resolve to `bundle exec pod <X>` which should ensure that `pod` commands will fail if they would not resolve to the version installed by the bundler

(In fact, `bundle install` installs its own executable commands under `.direnv/bin/`, but… you first have to run `bundle install` to have them, fail on `bundle exec pod…` should make it clear for the developers to install pods this way.)

This commit also updates Pods of `react-native-safe-area-context` in `bare-expo`.

# Test Plan

- Ran `where pod`, verified that `/Users/sjchmiela/Applications/expo/bin/pod` is on the list.
- Ran `bundle exec pod install` in `ios`, verified that it installs pods properly
- Ran `pod install`, verified that it installs pods properly

show more ...

[workspace] Install extra Ruby deps (#7851)

# Why

We want to keep a single version of `cocoapods` and `xcpretty` among the contributors too.

# How

Added the `cocoapods` and `xcpretty` to ro

[workspace] Install extra Ruby deps (#7851)

# Why

We want to keep a single version of `cocoapods` and `xcpretty` among the contributors too.

# How

Added the `cocoapods` and `xcpretty` to root `Gemfile`.

# Test Plan

I have confirmed that once the gems are installed and we go out from the workspace and into, again, `pod` resolves to `pod` installed from the `Gemfile` (eg. `/Users/sjchmiela/Applications/expo/.direnv/bin/pod`).

show more ...

Remove nix