Cloud Firestore 0.9.7 stucks at Installing BoringSSL-GRPC (0.0.2) during pod install

[iampawan]

Tried downgrading the version but didn't work. I am using the latest Xcode and IOS version.
Help @shihaohong @Hixie @jonahwilliams @pepegich

[dmvvilela]

Did you managed to fix this @iampawan ?

[iampawan]

Yes, somehow it got fixed @dmvvilela

[muhammadzumair]

@iampawan how did you fix it

[dmvvilela]

@muhammadzumair i got it to work too.. some problem with cocoa pods.. had to clean, make some pod update, change cocoapods version and tested a lot of stuff.. and it took a while but now it works again.

[jafar-albadarneh]

I've updated the cocoapods in order to fix the issue.
sudo gem install cocoapods

[balajiks-dev]

Hey guys, how did you fix this issue? I'm struggling here. @dmvvilela @iampawan

[Chizinski]

@dmvvilela Kindly outline how you solved the issue?

[dmvvilela]

@Chizinski I don't remember very well.. it was something to do with cocoa pods.. I was on an old version, tried cleaning things, upgrading, etc.. I don't know for sure what did the trick back then.

[MobileMon]

I was having this issue too. After upgrading cocoapods, flutter, and my pubspec to the latest versions, I thought the problem was still occurring. Turns out I just had to be patient and let BoringSSL install

To upgrade cocoapods:
sudo gem install cocoapods

To upgrade flutter
flutter upgrade

[nifrasismail]

seems it is because of the spec download from the repo, you may do it manually and notice it.

cd ~/.cocoapods/repos

git clone --depth 1 https://github.com/CocoaPods/Specs.git master

you may notice the size of the repo is approximately 800MB

after this pod install is not slow

[ch-muhammad-adil]

Let it install for a while, Actually it takes some time like 10-15 minutes.

[YuyaAbo]

I was able to install too. In fact, it took a few tens of minutes.

[AndrewPiterov]

it took around 30 minutes

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.