Crashlytics Pod install error on deployment to fast lane

Question & Answer Builds
1

I get the following error during my building whilst trying to deploy to iTunes connect related to the CRASHLYTICS cocoapod:

Installing Crashlytics (3.8.3)

Http download
$ /usr/bin/curl -f -L -o /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/d20170210-1249-9kin9l/file.zip https://kit-downloads.fabric.io/cocoapods/crashlytics/3.8.3/crashlytics.zip --create-dirs --netrc-optional
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
 0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

curl: (35) Server aborted the SSL handshake

[!] Error installing Crashlytics
[!] /usr/bin/curl -f -L -o /var/folders/90/5stft2v13fb_m_gv3c8x9nwc0000gn/T/d20170210-1249-9kin9l/file.zip https://kit-downloads.fabric.io/cocoapods/crashlytics/3.8.3/crashlytics.zip --create-dirs --netrc-optional

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed

0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
0 0 0 0 0 0 0 0 --:–:-- --:–:-- --:–:-- 0
curl: (35) Server aborted the SSL handshake

Any help much appreciated!

Thanks

2

Did you try to rebuild?

Also, does the error come from fastlane?

1 Like
3

Hi,
Yes rebuilt twice, it was working fine 10 mins before it failed,

Yes from fast lane, its when the build tries Downloading dependencies from the pod file.

It states that there is a new version of cocoa pods available… do you think this could be an issue? I doubt it though as it was working all of the today up till this point.

Thanks

4

You might want to report this on fastlane’s issue tracker instead, there was absolutely no update today on the build machines. There was a fastlane step update, but that should not cause an issue like this, and that only affects you if you upgraded to use the latest fastlane step version.

1 Like
5

Alright will certainly do this, thank you mate! appreciate it

1 Like
6

Sure, no problem, let us know how it goes!

1 Like
7

Any luck finding the cause of the issue @haiderashfaq?

8

I just rebuild for 11th time and it worked :confused:

9

Based on the error

It seems like a server issue “on the other side”.

Did the error happen again since (after the 11th rebuild)?

1 Like
10

nope did not happen again :slight_smile:

1 Like
11

Then I’d say it’s almost sure that the issue was on the other server.

Thanks for reporting @haiderashfaq! :wink:

1 Like