Error when installing mailcore2-ios using CocoaPods

[shukerullah]

I encountered an issue when attempting to install the mailcore2-ios library using CocoaPods. The installation process fails with the following error message:

[!] Error installing mailcore2-ios
[!] /usr/bin/curl -f -L -o /var/folders/bj/92jl9bk97td1pbrhlt2xr8800000gp/T/d20231102-5004-1ubi2z4/file.zip http://d.etpan.org/mailcore2-deps/mailcore2-ios/mailcore2-ios-12.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.11.0 cocoapods-downloader/1.4.0'

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:05 --:--:--     0
curl: (7) Failed to connect to d.etpan.org port 80 after 5065 ms: Couldn't connect to server

System and libraries information:

System:
    OS: macOS 12.6.8
    CPU: (4) x64 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz
    Memory: 32.57 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.11.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.0.0 - /usr/local/bin/npm
    Watchman: 2021.10.18.00 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.11.0 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: 4.2 AI-202.7660.26.42.7351085
    Xcode: 14.2/14C18 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.16 - /usr/bin/javac
    Python: Not Found
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0 
    react-native: 0.62.2 => 0.62.2 
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Please let me know if there is any additional information needed or if you have any suggestions on how to resolve this compatibility issue. Thank you for your assistance.

[PauliusVindzigelskis]

I'm getting similar error. I'm on Apple silicon (M1)

[!] Error installing mailcore2-ios
[!] /usr/bin/curl -f -L -o /var/folders/fl/j74103ds1w3_fjvq2ppqybnc0000gp/T/d20231102-64275-n58ycb/file.zip http://d.etpan.org/mailcore2-deps/mailcore2-ios/mailcore2-ios-12.zip --create-dirs --netrc-optional --retry 2 -A 'CocoaPods/1.14.2 cocoapods-downloader/2.0'

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:01:15 --:--:--     0
curl: (28) Failed to connect to d.etpan.org port 80 after 75009 ms: Couldn't connect to server
Warning: Problem : timeout. Will retry in 1 seconds. 2 retries left.
  0     0    0     0    0     0      0      0 --:--:--  0:01:14 --:--:--     0
curl: (28) Failed to connect to d.etpan.org port 80 after 74984 ms: Couldn't connect to server
Warning: Problem : timeout. Will retry in 2 seconds. 1 retries left.
  0     0    0     0    0     0      0      0 --:--:--  0:01:15 --:--:--     0
curl: (28) Failed to connect to d.etpan.org port 80 after 75000 ms: Couldn't connect to server

[!] 'mailcore2-ios' uses the unencrypted 'http' protocol to transfer the Pod. Please be sure you're in a safe network with only trusted hosts. Otherwise, please reach out to the library author to notify them of this security issue.

[PauliusVindzigelskis]

I am able to overcome this issue by replacing the pod with Swift Package pointing to master. It might work with pointing the pod to master, but haven't tried that

[HenryQuan]

It seems to work now with Cocoapods, was broken Last Friday.

[ju135]

This is because the site where the source code is hosted (etpan.org) is down from time to time (see the podspec) I forked the repository and hosted the binary in it. If you run into issues again, you can take a look at the readme of my fork - maybe this helps.

[wyllys66]

This is because the site where the source code is hosted (etpan.org) is down from time to time (see the podspec) I forked the repository and hosted the binary in it. If you run into issues again, you can take a look at the readme of my fork - maybe this helps.

Thank You! I started down this same path, but then found your fork. Much appreciated.