Xcode 10.2 Update issue Build system error -1: Unable to load contents of file list: input/output xcfilelist

Ios Problem Overview

After upgrading to Xcode 10.2 I am getting 2 errors

> :-1: Unable to load contents of file list: 'xxxxx/Pods/Target Support > Files/Pods-xxxx/Pods-xxxxx-frameworks-Debug-input-files.xcfilelist' > (in target 'xxxxx') > > > > :-1: Unable to load contents of file list: 'xxxxx/Pods/Target Support > Files/Pods-xxxxx/Pods-xxxxx-frameworks-Debug-output-files.xcfilelist' > (in target 'xxxxx')

I updated all my pod and changed build system to "Legacy Build System" but still getting the same build error

Ios Solutions

Solution 1 - Ios

I struggled with this for several hours today and this is what finally worked for me:

sudo gem update cocoapods --pre
pod update
clean
build

From what I've read, this is an issue with the new build process that is enabled by default in Xcode 10.2 though I've not found the workaround clearly documented anywhere yet. There may be a more elegant solution than what I described.

Solution 2 - Ios

delete 'Pods/', 'Podfile.lock', 'yourappname.xcworkspace'
pod deintegrate
pod install

it's work for me

I have encountered this problem every time, using the above method to solve, I do not know why, how to completely solve

Solution 3 - Ios

To illustrate the answer of @nfranzmeier:

Go to your project:

Select the right target
Build Phases
Unfold [CP] Embed Pods Frameworks script phase
Remove the files under Input Files Lists and Output Files Lists sections by selecting each of them and clicking on the - button

And you're done!

Solution 4 - Ios

None of the solutions above worked for me. What did the trick was:

Go to Xcode > Project > Info > Configurations
Set the values for Debug > Pods-XXX.debug and Release = Pods-XXX.release

This solved the issue for me on Xcode 12.0 beta

Solution 5 - Ios

Just pod install fixes this.

You don't necessarily want to update your pods (especially if you have not locked in versions explicitly). We had this error after creating a new Scheme.

Solution 6 - Ios

This solved my problem:

Open **Terminal**
1) run -> pod deintegrate
2) run -> pod install

In **Xcode**
3) Click Product Menu
4) Keep Pressing Option Button
5) Click Clean Build Folder
6) Run

Solution 7 - Ios

You can just edit your xxxx.xcodeproj/project.pbxproj file and delete the offending lines xxxinput-files.xcfilelist and xxxoutput-files.xcfilelist from the inputFileListPaths() outputFileListPaths() so they're empty again and then save it and rebuild

Solution 8 - Ios

I had changed the Run Configurations, from: Debug to DEV, but didn't change the Scheme:

On top left, select your project name, next to your device:

Then, select your project and click "Edit"

Last, change from Debug to your desired "Run configuration", in my case was DEV:

Do that, for every single one in the list on the left, but for Profile, leave that one as Release or your equivalent:

Solution 9 - Ios

For me, this was caused because I was setting up a custom configuration (.xcconfig) file for different environments. I wasn't importing the Pods/Target Support Files/Pods-XXXXXX/Pods-XXXXXX.release.xcconfig into my configuration file.

This guide helped me find the missing step. https://thoughtbot.com/blog/let-s-setup-your-ios-environments

Thanks Patrick.

Solution 10 - Ios

In my case the error happened when archiving the app.

The cause was that the wrong build configuration was selected in the build scheme. This happened after introducing xcconfig-files for staging environment.

How i fixed it:

select the build scheme in Xcode (next to the "play" button)
select product -> scheme -> edit scheme
check if the correct build scheme is selected

see here:

Solution 11 - Ios

In my case 
 -> pod deintegrate
 -> pod clean 
 -> pod install 
 then rebuild the project works fine. 
 My XCode = 11.3.1

Solution 12 - Ios

This worked out for me:

cd ios && pod deintegrate

pod install

Then go ahead and rerun your project

Solution 13 - Ios

cd ios

rm Podfile.lock

edit Podfile as below

# Uncomment this line to define a global platform for your project
platform :ios, '10.0'
>> Uncommented and bumped the version to 10

flutter clean

flutter pub get

pod repo update

pod update

Solution 14 - Ios

For me (using Mac Mojave) using the above solutions didn't work..

I manage to successfully overcome this issue by installing RVM on my Mac via:

curl -L https://get.rvm.io | bash -s stable --auto-dotfiles --autolibs=enable --rails

As described on this page.

And then re-install cocoapods via:

gem install cocoapods

And lastly run again:

pod install

I hope this helps someone who was stuck endlessly like me :)

Solution 15 - Ios

I have the same issue and do the below steps and now am able to make build successful

go to Project->Configurations and set the valid configuration file for configuration.
if you see already set correct valid configuration file then do pod install
if you are not able see valid configuration file then pod install and Now you can see the valid configuration file just choose the right one now.

Note : I have this issue on Xcode 11.7

Solution 16 - Ios

These are the steps that worked for me:

In the terminal, inside of project document, type:

pod update
If pod is not found, you should install Cocoapods:

sudo gem install cocoapods
If it returns a ruby/gem error, you should install (or reinstall) Ruby:

curl -L https://get.rvm.io | bash -s stable

rvm install ruby-2.7.2

sudo gem install cocoapods
Try to update pods again, and when it is finished, open .xcworkspace file.

Solution 17 - Ios

I solve the cloud_firestore not found the issue as well by this after integrating a new version of that cloud_firestore. (optional) update the podfile with the required version of cloud_firestore for fast compiling (saves 500k+ lines of execution).

delete 'Pods/', 'Podfile.lock', 'yourappname.xcworkspace'

pod deintegrate