-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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
Long pod install step should indicate progress #8983
Comments
|
My actual revision is 2599967. I have a local commit for my personal cert. |
I bet this is the CocoaPods The first time you run At a minimum we should output a message informing the user. I'll file a bug. |
Should we have a benchmark that measures "time to create a new app", so we don't accidentally regress it? |
Yup. It's
|
Steps to ReproduceOn a macOS machine:
You'll get a 5-10 minute hang with no progress message as CocoaPods pulls down close to 400MB of specs, but no progress message indicating what's happening. For people using CocoaPods, this one-time bootstrapping step is probably unavoidable, but we should output a message indicating that this is going on. As @eseidelGoogle notes, maybe just stream CocoaPods output? |
/cc @jakobr-google |
flutter create
fails to build
Well, it takes about 20m, but it does work. :) I think we should consider making this an explicit install step instead of having it implicit in |
#8999 has part of this. We should update the 'setup' webpage as well. |
CocoaPods needs to download the master spec repo, which can take quite a while. Adding a `pod setup` step to the installation instructions, so users take the hit during install, instead of on the first build. Fixes flutter/flutter#8983.
CocoaPods needs to download the master spec repo, which can take quite a while. Adding a `pod setup` step to the installation instructions, so users take the hit during install, instead of on the first build. Moved CocoaPods installation steps to a separate section, since they are needed for Simulator builds as well. Fixes flutter/flutter#8983.
CocoaPods needs to download the master spec repo, which can take quite a while. Adding a `pod setup` step to the installation instructions, so users take the hit during install, instead of on the first build. Moved CocoaPods installation steps to a separate section, since they are needed for Simulator builds as well. Fixes flutter/flutter#8983.
Read some background which was interesting. Seems like it was an explicit choice to clone the entire git tree instead of a shallow working directory clone to avoid continuous costs on each pod update. But I suspect it's going to cost more and more as a first step as time goes on. Unfortunately I don't see any open issues in https://github.com/cocoapods/cocoapods/issues to rework their CDN mechanism in general... |
After an hour i get this:
|
really too much
|
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 run
silently hangs on the command line.If I open
ios/Runner.xcworkspace
and build there, I get:clang: error: no such file or directory: '/src/bug5823/ios/Pods/Target Support Files/Pods-Runner/Pods-Runner-dummy.m'
clang: error: no input files
The text was updated successfully, but these errors were encountered: