After spending an excellent period of time troubleshooting this concern in my Xcode / React Native undertaking, I lastly cracked the issue associated to GoogleService-Information.plist not being present in my undertaking.

error: Construct enter file can't be discovered: '/Customers/expo/workingdir/construct/frontend/cell/ios/GoogleService-Information.plist'. Did you neglect to declare this file as an output of a script part or customized construct rule which produces it?

The error was fairly annoying at first, however after some trial &. error, I managed to discover a working answer.

1. I opened my undertaking in Xcode.

2. Launch Xcode and open your undertaking. Navigate to Your Goal’s Construct Phases.

3. Click on on the undertaking file (the blue icon) on the prime of the Mission Navigator. Choose your app’s goal from the listing. Add or Edit a Run Script Part:

4. Go to the “Construct Phases” tab.

ATTENTION:

If you have already got a script part that ought to produce GoogleService-Information.plist, click on on it to increase and edit the script.

If you do not have a related script part, add one by clicking the ‘+’ button on the prime left of the “Construct Phases” part, then select “New Run Script Part”.

5. Within the script editor space, write or modify the script that generates or modifies GoogleService-Information.plist.

MAKE SURE:

Be sure that the script writes the output file to the right location, usually to $(SRCROOT), $(BUILT_PRODUCTS_DIR), or $(TARGET_BUILD_DIR) relying in your undertaking construction and necessities.
Specify Output Information (Non-compulsory):

SOLUTION

Under the script editor, you might even see an space to specify “Output Information” or “Output Information Checklist”.

Right here, you may add the trail the place the script will place GoogleService-Information.plist. For instance:

14. Enter the anticipated path of the GoogleService-Information.plist file, like:

    $(SRCROOT)/GoogleService-Information.plist // <-- If undertaking in Root PATH.
    

    or like

    $(SRCROOT)/path/to/GoogleService-Information.plist // <-- If undertaking in nested PATH.
    

15. This step, whereas not necessary, turned out to be fairly insightful for incremental builds. It’s a great way to let Xcode know when it must re-run the script.

16. I then ran a brand new construct on my expo undertaking after cleansing my xcode construct folder.