Skip to content

[FR] Change the default cocoapods source to the CDN #470

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
polmum opened this issue Oct 6, 2021 · 1 comment · Fixed by #502 or #509
Closed

[FR] Change the default cocoapods source to the CDN #470

polmum opened this issue Oct 6, 2021 · 1 comment · Fixed by #502 or #509

Comments

@polmum
Copy link

polmum commented Oct 6, 2021

Feature proposal

  • EDM4U Component: iOS Resolver

Cocoapods changed the default spec repo source to one that uses a CDN on version 1.8. If no source is defined by the Podfile, the CDN source will be the one to be used.
The EDM4U iOS cocoapods component is hardcoding the old repo: https://github.com/CocoaPods/Specs.git, which is significantly slower.
Updating the repo here would be the most straightforward solution. Alternatively, we could either let the default repo be configured by users (defaulting to the CDN one), or remove that logic altogether, and let cocoapods default to the correct repo source.

@google-oss-bot
Copy link

This issue does not seem to follow the issue template. Make sure you provide all the required information.

@paulinon paulinon removed the new to be triaged label Oct 6, 2021
@googlesamples googlesamples locked and limited conversation to collaborators Mar 27, 2022
chkuang-g added a commit that referenced this issue Apr 4, 2022
- Version 1.2.170 - Apr 4, 2022
* Android Resolver - Fixes #498 - Fix the path separator of the Maven repo
  injected to `mainTemplate.gradle`.
* iOS Resolver - Fixes #470 - Switch default Cocoapods master repo from Github
  to CDN.
* iOS Resolver - `Link Framework Statically` setting is now default to `true`.
  That is, `use_frameworks! :linkage => static` will be added to `Podfile` by
  default instead of `use_frameworks!`. This can be changed in iOS Resolver
  settings. This fixes odd behaviors when pods include static libraries, ex.
  Firebase Analytics.
* iOS Resolver - Added a workaround when app crashes on launch due to
  `Library not loaded: @rpath/libswiftCore.dylib` when some pods includes Swift
  framework. This is turned `OFF` by default and can be changed in iOS Resolver
  settings.
chkuang-g added a commit that referenced this issue Apr 4, 2022
- Version 1.2.170 - Apr 4, 2022
* Android Resolver - Fixes #498 - Fix the path separator of the Maven repo
  injected to `mainTemplate.gradle`.
* iOS Resolver - Fixes #470 - Switch default Cocoapods master repo from Github
  to CDN.
* iOS Resolver - `Link Framework Statically` setting is now default to `true`.
  That is, `use_frameworks! :linkage => static` will be added to `Podfile` by
  default instead of `use_frameworks!`. This can be changed in iOS Resolver
  settings. This fixes odd behaviors when pods include static libraries, ex.
  Firebase Analytics.
* iOS Resolver - Added a workaround when app crashes on launch due to
  `Library not loaded: @rpath/libswiftCore.dylib` when some pods includes Swift
  framework. This is turned `OFF` by default and can be changed in iOS Resolver
  settings.
chkuang-g added a commit that referenced this issue Apr 6, 2022
- Version 1.2.170 - Apr 4, 2022
* Android Resolver - Fixes #498 - Fix the path separator of the Maven repo
  injected to `mainTemplate.gradle`.
* iOS Resolver - Fixes #470 - Switch default Cocoapods master repo from Github
  to CDN.
* iOS Resolver - `Link Framework Statically` setting is now default to `true`.
  That is, `use_frameworks! :linkage => static` will be added to `Podfile` by
  default instead of `use_frameworks!`. This can be changed in iOS Resolver
  settings. This fixes odd behaviors when pods include static libraries, ex.
  Firebase Analytics.
* iOS Resolver - Added a workaround when app crashes on launch due to
  `Library not loaded: @rpath/libswiftCore.dylib` when some pods includes Swift
  framework. This is turned `OFF` by default and can be changed in iOS Resolver
  settings.
chkuang-g added a commit that referenced this issue Apr 6, 2022
- Version 1.2.170 - Apr 4, 2022
* Android Resolver - Fixes #498 - Fix the path separator of the Maven repo
  injected to `mainTemplate.gradle`.
* iOS Resolver - Fixes #470 - Switch default Cocoapods master repo from Github
  to CDN.
* iOS Resolver - `Link Framework Statically` setting is now default to `true`.
  That is, `use_frameworks! :linkage => static` will be added to `Podfile` by
  default instead of `use_frameworks!`. This can be changed in iOS Resolver
  settings. This fixes odd behaviors when pods include static libraries, ex.
  Firebase Analytics.
* iOS Resolver - Added a workaround when app crashes on launch due to
  `Library not loaded: @rpath/libswiftCore.dylib` when some pods includes Swift
  framework. This is turned `OFF` by default and can be changed in iOS Resolver
  settings.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
3 participants