Realm-cocoa: Stack on "Downloading dependency: sync 3.0.0"

[NikKovIos]

When i did updating a pods withpod update --verbose

-> Installing Realm 3.2.0 (was 3.1.1)
 > Git download
 > Git download
     $ /usr/bin/git clone https://github.com/realm/realm-cocoa.git /var/folders/s4/fbkdf48j71l81l198j5n86q80000gn/T/d20180319-10484-1xkd5be --template= --single-branch --depth
     1 --branch v3.2.0
     Cloning into '/var/folders/s4/fbkdf48j71l81l198j5n86q80000gn/T/d20180319-10484-1xkd5be'...
     Note: checking out '78eca82282e611e76fcf8bf414db0ea912816ddd'.

     You are in 'detached HEAD' state. You can look around, make experimental
     changes and commit them, and you can discard any commits you make in this
     state without impacting any branches by performing another checkout.

     If you want to create a new branch to retain commits you create, you may
     do so (now or later) by using -b with the checkout command again. Example:

       git checkout -b <new-branch-name>

     $ /usr/bin/git -C /var/folders/s4/fbkdf48j71l81l198j5n86q80000gn/T/d20180319-10484-1xkd5be submodule update --init --recursive
     Submodule 'Realm/ObjectStore' (https://github.com/realm/realm-object-store.git) registered for path 'Realm/ObjectStore'
     Cloning into '/private/var/folders/s4/fbkdf48j71l81l198j5n86q80000gn/T/d20180319-10484-1xkd5be/Realm/ObjectStore'...
     Submodule path 'Realm/ObjectStore': checked out 'f2a536d29de48e34e60799a5bf3f36e13806387e'
     Submodule 'external/catch' (https://github.com/philsquared/Catch) registered for path 'Realm/ObjectStore/external/catch'
     Cloning into '/private/var/folders/s4/fbkdf48j71l81l198j5n86q80000gn/T/d20180319-10484-1xkd5be/Realm/ObjectStore/external/catch'...
     Submodule path 'Realm/ObjectStore/external/catch': checked out 'ee67ac6b7c3595251342671485c65cf81d725896'
 > Running prepare command
   $ /bin/bash -c  set -e sh build.sh cocoapods-setup
   core is not a symlink. Deleting...
   Downloading dependency: sync 3.0.0

And it tooks forever. I think that it is a host problem.

[bmunkholm]

We don't experience any problems with this as we are hosting these on S3. Perhaps it was a temporary issue.