1

I'm facing an issue while building my iOS project in Xcode. The error message is:

Library 'FirebaseCore' not found.
Linker command failed with exit code 1 (use -v to see invocation).

I have already tried the following:

  • Running pod install and ensuring FirebaseCore is listed in Podfile.lock.
  • Cleaning the build folder (Cmd + Shift + K) and restarting Xcode.
  • Checking that I'm opening the .xcworkspace file instead of .xcodeproj.
  • Ensuring my Pods directory is included in the project's Framework Search Paths.
  • Running pod deintegrate and pod install again.

My CocoaPods version: 1.16.2.

Despite these steps, the issue persists. The same project works fine in other Mac systems. Any suggestions on how to resolve this?

Improve this question
3
  • On Stack Overflow, please don't show pictures of text and code. Copy the text into the question itself and format it so that it's easy to read, copy, and search. You can edit the question to correct this using the edit link at the bottom. Commented Feb 27 at 15:12
  • It may also be helpful to include the podfile you're using. Commented Feb 27 at 19:01
  • Did you use -v to see what call is invoking it and the information associated with that call to further debug the issue? Commented Mar 3 at 18:49

1 Answer 1

Reset to default
1

I faced a similar issue, but instead of FirebaseCore, I was getting a "No WebKit found" error. Here’s what I’d suggest:

  1. Make sure you're using the latest Firebase configuration for your project and the latest pub dependencies.

  2. In my case, the solution was a bit different. I struggled with the error for two weeks but couldn't resolve it. Eventually, my MacBook broke down, and I had to buy a new one. On the new machine, I installed:

  3. The latest Flutter SDK.

  4. Updated Ruby on macOS.

  5. The latest CocoaPods.

  6. The latest Xcode.

  7. The latest Android Studio.

  8. Java 17.

My new Mac is an M2 Pro, and after setting everything up from scratch, the project ran perfectly on the first try.

Based on my experience, this issue seems to be related to Xcode, CocoaPods, or iOS development files. Since you mentioned that it works on another machine but not yours, this might be a system-level issue.

While this solution is a bit extreme, it worked for me. Hope it helps! Good luck!🚀

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.