Write a custom catalog title here
Unable to install Cocoapods on macOS Catalina 10.15.7 You’re now watching this thread and will receive emails when there’s activity. Click again to stop watching or visit your profile/homepage to manage your watched threads. CocoaPods Environment. Mac 10.15 / Catalina Brew based cocoapods - defaults to 2.3, instead of 'Current' This won't run due to reliance on deprecated Ruby 2.3 which does not exist on later Mac versions. Project that demonstrates the issue. Base Mac 10.15 install, install / upgrade cocoapods, then try to run. CocoaPods is a dependency manager which integrates dependencies into your Xcode workspace. To install it using RubyGems run: gem install cocoapods. To install Updates using Cocoapods, simply add the following line to your Podfile: pod 'Updates'. Then run the command: pod install. For more information see here. To install CocoaPods, you need Ruby. As a Mac user, you should already have Ruby installed on your system. Run the following command in your terminal to install CocoaPods (via Ruby): sudo gem install cocoapods. Since we have to use sudo, you’ll have to enter your system password to allow the install.
Because the black apple system was reinstalled on the previous computer, CocoaPods was reconfiguredCocoaPods
What is CocoaPods?
ocoaPods is a tool responsible for managing third-party open source libraries in iOS projects. The source code of the CocoaPods project is managed on GitHub (https://github.com/CocoaPods).
The development of iOS projects inevitably requires the use of third-party open source libraries. When using third-party libraries, in addition to importing source code, integration of these dependent libraries also requires us to manually configure, and when these third-party libraries are updated, we also need It is very troublesome to update the project manually.
The emergence of CocoaPods allows us to save the time of setting up and updating third-party open source libraries. With CocoaPods, we can manage the third-party dependent libraries in a unified manner. Configuration and update only need to be completed with a few simple lines of commands.
Why use CocoaPods?
Before using CocoaPods, when a development project needs to use a third-party open source library, we need to:
Copy the source code of the open source library into the project
Add some dependent frameworks and dynamic libraries
Set -Objc, -fno-objc-arc and other parameters
Manage their updates
After using CocoaPods, we only need to put the used open source libraries in a file named Podfile, and then execute pod update. CocoaPods will automatically download the source code of these third-party open source libraries and provide it for us Set the corresponding system dependencies and compilation parameters for the project.
The principle of CocoaPods
The principle of CocoaPods is to put all dependent libraries in another project called Pods, and then let the main project depend on the Pods project, thus moving the source code management work from the main project to the Pods project.
Third-party libraries will be compiled into .a static libraries or .framwork dynamic link libraries for our real projects.
CocoaPods will combine all third-party libraries into a project named Pods in the form of targets, which will be placed in the newly generated Pods directory. The entire third-party library project will generate a static library named libPods.a for our project to use.
For resource files, CocoaPods provides a bash script named Pods-resources.sh, which will be executed every time the project is compiled, copying various resource files of third-party libraries to the target directory.
The original project settings have been changed. At this time, if we directly open the original project file to compile, an error will be reported. The Pods project where our project and third-party library are located will be organized and managed in the form of a newly generated workspace, which is convenient for us to intuitively manage the project and third-party library.
CocoaPods uses a file named Pods.xcconfig to set all dependencies and parameters at compile time
CocoaPods installation steps
Ruby environment
1. Set up ruby source
The ruby environment that comes with the Mac system will be installed
1.1, check the ruby source of your computer
ruby -v
Legend has it that the minimum version of ruby supported by CocoaPods is 2.2.2. If your computer version is lower than this version, you can upgrade ruby. The above shows that my computer version does not need to be upgraded. You can ignore the following upgrade operation
sudo gem update --system
1.2 Replace ruby mirror
Ruby's default original address is a foreign network address. Use the following command to view the current mirrorgem sources -l
Remove current mirrorgem sources --remove https://rubygems.org/
Add domestic ruby mirrorgem sources -a https://gems.ruby-china.com/
Check the current mirror again and find that it has been replaced successfully
CocoaPods installation
Before Mac OS X 10.11sudo gem install cocoapods
After Mac OS X 10.11sudo gem install -n /usr/local/bin cocoapods
Since the system of this machine is 10.15, choose the latter command inputsudo gem install -n /usr/local/bin cocoapods
2.2, check whether the installation is successful
pod search AFNetworking
I actually looked at this blog configuration at the beginning, but at this step I found that there seems to be a problem
Opened the website https://git.coding.net/CocoaPods/Specs.git
found this look
But the principle is
The Podspec files of all projects are hosted at https://github.com/CocoaPods/Specs. When pod setup is executed for the first time, CocoaPods will update these podspec index files to the local ~/.cocoapods/ directory. This index file is relatively large, about 80M.
And I guess the reason for this is to clone the code of this repository
CocoaPods/Specs
https://github.com/CocoaPods/Specs.git
But the clone code from git is quite full, so it is put on coding, but this warehouse is out of date or private.
So I cloned a warehouse on Code Cloud
After changing the code link, it succeeded and the speed flew up
“dart” can’t be opened because apple cannot check it for malicious software.
“gen_snapshot” cannot be opened because the developer cannot be verified.
flutter macos
flutter clean in mac
brew flutter
flutter simulator
flutter mac app
After updating to MacOS 10.15 Catalina, there are problems with Flutter.
Specifically, Flutter doctor complaints about the following:
Downloaded executables cannot execute on host.
CocoaPods not installed.
It is important to explain that before updating, when my computer was running Mojave 10.14, these issues with Flutter did not exist, thus flutter doctor -v reported no issues whatsoever.
Regarding the first issue: Downloaded executables cannot execute on host.
Flutter doctor offers this link: https://github.com/flutter/flutter/issues/6207
Nevertheless, the linked article refers to Linux, not MacOS...
Regarding the second issue: CocoaPods not installed.
Flutter doctor suggests the following solution:
brew install cocoapods
pod setup
Nevertheless, although 'install cocoapods' works fine, 'pod setup' fails, indicating the following error:
Running flutter doctor -v offers the following result:
I humbly wish to ask for your help, please, to clarify what does it mean when it says Downloaded executables cannot execute on host?
and, what may be done to resolve it? Please?
also,if cocoapods was running beautifully when using Mojave 10.14, what may be the issue now, being seemingly unable to successfully run pod setup?
is anyone else here having any issues with Flutter after upgrading to MacOs 10.15 Catalina Beta, which you were not having before with Mojave?
THANK YOU !!!
Install Cocoa Pods In Mac Os Catalina Download
Update...Researching about this issue, I've encountered a very sad comment, which suggests that basically there is no support for Flutter in Catalina...
Please find it here:https://github.com/flutter/flutter/issues/34000
The comment says:Flutter is not yet supported on macOS 10.15, although we're obviously looking at it. This is a duplicate of #22598, which relates to the removal of 32-bit support from Catalina.
So, I am beginning to think that it might be a good idea to go back to Mojave's safety, at least Flutter was working fine...
Please share your thoughts, suggestions, advise?
Issues when using macos 10.15 & ios 13 · Issue #33909 · flutter , Crash report written to' I'm using Flutter stable v1.5.4-hotfix.2 on macOS Catalina v10.15 Beta (19A487m) on my 2015 MacBook Pro. One common macOS Catalina problem that people have encountered is that macOS 10.15 fails to download, with some users seeing an error message that says “macOS Catalina download has failed.' Others,
For this issue:
[!] Flutter (Channel dev, v1.7.11, on Mac OS X 10.15 19A487m, locale en-SE) ✗ Downloaded executables cannot execute on host. See https://github.com/flutter/flutter/issues/6207 for more information
Install Cocoa Pods In Mac Os Catalina Free
Easy fix:Open a terminal on MAC and run the following commands:
Enjoy
VersionCheckError during `flutter upgrade` on macOS 10.15 beta , VersionCheckError during `flutter upgrade` on macOS 10.15 beta (Catalina) #33890. Closed. timsneath opened this issue on Jun 4, 2019 · 22 comments. Flutter is not yet supported on macOS 10.15, although we're obviously looking at it. This is a duplicate of #22598, which relates to the removal of 32-bit support from Catalina. timsneath closed this on Jun 6, 2019 Mahdi-Hemmatnia commented on Sep 3, 2019 •
Uninstall and install it again (fe if you are using homebrew).
Just run:
Setting up Flutter on macOS Catalina - Alexandros Baramilis, Flutter has good installation documentation, but to install it on macOS Catalina Basically, if you created a new user account in macOS Catalina, zsh (Z shell) Type once again flutter doctor to see if there are any issues left. Flutter is not currently supported on macOS 10.15, but adding this issue for awareness. Flutter crash report; please file at https://github.com/flutter/flutter/issues.
VersionCheckError during `flutter upgrade` on macOS , Flutter is not currently supported on macOS 10.15, but adding this issue for awareness. Flutter crash report; please file at https://github.com/flutter/flutter/issues. For macOS Catalina, Apple has changed the way Gatekeeper verifies binaries downloaded from the internet (reference), and apparently disabled the 'open anywhere' option from System Preferences. Currently, using the flutter tool is not possible unless the user runs sudo spctl --master-disable from the command line reference.
Flutter.dev and the problem with macOS Catalina (Gatekeeper), [✓] Flutter (Channel stable, v1.9.1+hotfix.4, on Mac OS X 10.15 19A583, locale de-DE) • Flutter version 1.9.1+hotfix.4 at I've upgraded my Mac to 10.15 and iPhone to iOS13. Here're several problems I've met: gen_snapshot(i386) reports bad cpu type(i386 is not supported to run in macos 10.15) flutter doctor -v --verbose [!]
Flutter MacOS Catalina, Currently, flutter macOS engine binaries are manually codesigned and notarized with Apple prior to each dev release. This issue is to track the process of This knowledge base article provides information about support for macOS 10.15 Catalina, as well as known issues. It is highly advisable to read the known issues as there are several unavoidable issues in this OS release. Apple has new enforced per application permissions in this version.
Comments
- thank you immensely !!! indeed, the problem regarding CocoaPods indeed has now been resolved !!!
- Flutter Doctor now says: Xcode - develop for iOS and macOS (Xcode 10.2.1) • Xcode at /Applications/Xcode.app/Contents/Developer • Xcode 10.2.1, Build version 10E1001 • CocoaPods version 1.7.4
- nevertheless, the other issue still remains, which says: Downloaded executables cannot execute on host. Do you have any idea how may this other issue be resolved? THANK YOU !!!
- Upgrading from Mojave to Catalina, this fixed my flutter build issues. Thank you