Errno::ENOENT - No such file or directory @ rb_sysopen (scloans.podspec.json)

[indrajit-roy-sc]

Error

Errno::ENOENT - No such file or directory @ rb_sysopen - /Users/ifnow/Desktop/mobilePlannerFlutter/mob_app/ios/Pods/Local Podspecs/scloans.podspec.json
/opt/homebrew/lib/ruby/gems/3.4.0/gems/cocoapods-core-1.16.2/lib/cocoapods-core/specification.rb:690:in 'IO.read'
...

Expected

pod update should work

Actual

pod update fails

[indrajit-roy-sc]

Solution / Workaround

The key is to temporarily revert to the last known good state to allow Flutter's tooling to regenerate the missing files, and then perform the upgrade.

Step 1: Revert to the Old Version

In your pubspec.yaml, change the package version back to the one that is currently in your ios/Podfile.lock.

# pubspec.yaml

dependencies:
  flutter:
    sdk: flutter

  # Revert this line from 2.0.0 back to the last working version
  package_name: 1.0.0 

Then, run flutter pub get from your terminal.

Step 2: Regenerate the Podspec File

Run your app. The easiest way is to execute flutter run from your project's root directory.

flutter run

This command will trigger Flutter's build process, which now succeeds because your pubspec.yaml matches the Podfile.lock. As part of this process, it regenerates the missing .podspec file inside the .symlinks directory. You don't need to let the app finish building; you can stop the command once you see that the Xcode build phase has started successfully.

Step 3: Update to the New Version

Now that the necessary files exist, go back to your pubspec.yaml and update the package to the new version you originally wanted.

# pubspec.yaml

dependencies:
  flutter:
    sdk: flutter

  # Now, update to the new version
  package_name: 2.0.0 

Run flutter pub get one more time.

Step 4: Run Pod Update

Finally, navigate to your ios directory and run pod update.

cd ios
pod update

This command should now complete successfully because CocoaPods can find the package_name.podspec file and will correctly handle updating it from version 1.0.0 to 2.0.0.

Hope this helps anyone else stuck in this loop