| #
539625ca |
| 01-Jun-2020 |
Stanisław Chmiela <[email protected]> |
[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 ...
|
| #
f420a620 |
| 22-Nov-2019 |
Stanisław Chmiela <[email protected]> |
[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`, reinsta
[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.
show more ...
|
| #
8a2243a1 |
| 30-Aug-2019 |
Stanisław Chmiela <[email protected]> |
[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
[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
show more ...
|