wcdean217
wcdean217

Reputation: 277

FBLPromises Framework not found

I am tryin to install Firebase using cocoapods so I may send push-notifications to user devices. However, everytime I follow the instructions step by step, I get this error that says "framework not found FBLPromises". Anyone have any ideas how to fix? Everything I have looked up online does not work.

Upvotes: 25

Views: 42962

Answers (11)

IbrahimShazly
IbrahimShazly

Reputation: 33

I faced the same problem while using flutter!
These are the only steps that worked for me based on this issue :

  1. delete podfile.lock
  2. flutter clean
  3. pod deintegrate
  4. pod cache clean --all
  5. flutter pub get
  6. pod install
  7. pod update
  8. open runner.xcworckspace then build
    I wasted 3 days of my life on this ! Honestly, the flutter ecosystem needs huge improvements!

Upvotes: 2

zouritre
zouritre

Reputation: 655

To anyone that has this issue when installing Firebase SDK with SPM, go to your build settings and remove the framework from Other Linker Flags if it is present.

Linker flags

The issue (re)appeared after I migrated the SDK from Cocoapods to SPM. It seems that every framework and their dependencies installed from cocoapods get listed in the linker flags while those of SPM doesn't. So you may also remove all traces of the Cocoapods FB librairies from the flags I think.

Upvotes: 6

drongal
drongal

Reputation: 131

if anyone is still struggling with that: add $(inherited) to your app FRAMEWORK_SEARCH_PATHS for building and release.

Upvotes: 0

Haffez Mohamed
Haffez Mohamed

Reputation: 89

Go to your Pod target and set Build Active Architecture Only = YES For Debug Environments enter image description here

Upvotes: -1

  1. Open Podfile by typing the command open Podfile in the folder of the project using the terminal.

  2. Type pod Promises

Done

Upvotes: -4

Hocine B
Hocine B

Reputation: 389

Click on the project > Targets. Select your target. Then click on Build Settings. Find "Runpath searches path" and add "$(PODS_CONFIGURATION_BUILD_DIR)/PromisesObjC". It worked for me, but it gave me another error dealing with another missing lib, so I had to do it again until all libs were found.

Upvotes: 0

PhoneyDeveloper
PhoneyDeveloper

Reputation: 1150

Simply setting Build Active Architecture: Debug - Yes, Release - No fixed this for me. I had it set to No, No before. I think this matches the setting in the Pods project.

Upvotes: -2

Rahul Panzade
Rahul Panzade

Reputation: 1372

Go to your Pod target and add arm64 in Excluded Architecture

enter image description here

Upvotes: 4

Declan Maybury
Declan Maybury

Reputation: 21

I was having the same issue, and I solved it by going to Product > Scheme > Edit Scheme... and selecting Find Implicit Dependencies. After that, the project was able to build correctly.

Upvotes: 1

cooldude22
cooldude22

Reputation: 21

Probably late but I managed to fix it by linking FBL promises in my podfile to the rest of the project!

Upvotes: 0

Neloy Kundu
Neloy Kundu

Reputation: 673

The following worked for me:

What probably happened (for anyone still looking) is that after running

    pod install

in your project's directory, you are still building the ".xcodeproj" file instead of running the newly created ".xcworkspace" from the pod install. Remember, after pod installing, you MUST do edits on and work with the .xcworkspace instead.

Upvotes: 56

Related Questions