![]() ![]() Open up you Xcode project and configure your provisioning and signing profile. Try rebuilding the app, knowing that it will fail. Gem uninstall cocoapods gem install cocoapods -v 1.7.5 Temporarily revert back to cocoapods 1.7.5. ![]() Rm -rf ios/Podfile ios/Podfile.lock pubspec.lock ios/Pods ios/Runner.xcworkspace Then clean it with the following commands. StepsĬreate a backup of your project first. This is a one time operation if you don’t clean your Xcode projects that often. The solution is temporarily reverting back to cocoapods 1.7.5 and recreating the Xcode project from scratch. ![]() If you are using cocoapods version 1.8.0 or greater, it is likely that your builds will fail with a similar error to this.Įrrno::ENOENT - No such file or directory rb_sysopen A Podfile is a script that declares 3rd party iOS dependencies written in Swift or Objective-C. When you build an iOS app with Flutter for the first time or on a cleaned build state, Flutter creates a new Xcode workspace set up with an automatically generated Podfile. While developing our TestFairy Flutter Plugin, I noticed an unusual bug happening during iOS builds, described as Errno::ENOENT - No such file or directory rb_sysopen.Īpparently, the latest Flutter builds sometimes misconfigured its Pods project which may cause this error. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |