en Copyright 2015 Java http://172.16.0.5:8080/history/expo/bin/pod#539625ca [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 List of files: /expo/bin/pod Mon, 01 Jun 2020 08:25:50 +0000 Stanisław Chmiela <sjchmiela@users.noreply.github.com> http://172.16.0.5:8080/history/expo/bin/pod#f420a620 [nix] Update dependencies (#6346)# Why 1. We've been using not-latest, beta version of CocoaPods for a while. 2. New Yarn version was available. # How Ran `./update-dependencies`, reinstalled pods in both `ios` and `bare-expo/ios`. # Test Plan Both projects should build. List of files: /expo/bin/pod Fri, 22 Nov 2019 08:50:57 +0000 Stanisław Chmiela <sjchmiela@users.noreply.github.com> http://172.16.0.5:8080/history/expo/bin/pod#8a2243a1 [ios] Enable CocoaPods 1.8 improvements (#5502)# Why Closes https://github.com/expo/expo/issues/4667. # How - upgraded CocoaPods to 1.8.0.beta1 - enabled CocoaPods improvements - grouped offending Facebook dependencies together so they can access each other # Test Plan Expo client builds and runs ok List of files: /expo/bin/pod Fri, 30 Aug 2019 18:39:57 +0000 Stanisław Chmiela <sjchmiela@users.noreply.github.com> http://172.16.0.5:8080/history/expo/bin/pod#2c0536a8 Create and use bin/nix-binstubs List of files: /expo/bin/pod Tue, 11 Dec 2018 22:12:18 +0000 Nick Novitski <nick@expo.io>