Library not loaded: @rpath/FBLPromises.framework/FBLPromises iOS 13.3.1

25.1k Views Asked by At

My app crashes on lunch and getting this error:

dyld: Library not loaded: @rpath/FBLPromises.framework/FBLPromises
  Referenced from: /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Zeta
  Reason: no suitable image found.  Did find:
    /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises: code signature invalid for '/private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises'

    /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises: stat() failed with errno=25
    /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises: code signature invalid for '/private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises'

    /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises: stat() failed with errno=1
    /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises: code signature invalid for '/private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises'

    /private/var/containers/Bundle/Application/11X3EC15-5A16-4E27-AC4A-FB0503E6F1E2/Zeta.app/Frameworks/FBLPromises.framework/FBLPromises: stat() failed with errno=1
(lldb)

I used it on my own device (iPhone 11 pro) iOS 13.3.1. It was working perfectly fine before I update my device to iOS 13.3.1 . My app also works perfectly fine on the simulator (iPhone 11 - iOS 13.3). Using Xcode 11.3.1.

Removing the profile from my device and trusting again didn't work.

UPDATE: Tried to build it using Xcode Beta 11.4 and didn't work.

UPDATE II:

  • The only pods that I'm using are Firebase/Auth, Firebase/Core, Firebase/Firestore.
  • Commenting use_frameworks! and using use_modular_headers! gave me these errors: Showing Recent Issues The iOS deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to 4.3, but the range of supported deployment target versions is 8.0 to 13.2.99. (For all the pods in the project)
12

There are 12 best solutions below

9
On BEST ANSWER

You are probably using free developer account. Apple blocked utilizing external frameworks on free accounts with 13.3.1 upgrade. Try downgrading to 13.3 if still possible or buy Apple Developer License.

UPDATE 04/2020: Upgrading to iOS 13.4 and XCode 11.4 currently solves this issue.

0
On

Open the file extension and make sure it's in the library.

Open Xcode -> Products -> YourApp.app -> "Show in Finder"

And you see

"YourApp.app" -> This file "right click" and click -> "Show package contents"

If libraries are missing here, you need to check their framework connections.

0
On

I tried commenting out the line # use_frameworks! in the pod file and it worked

1
On

Probably the problem on the Xcode or the framework itself, I was got the same error on Xcode 11.4 beta and iOS 13.4 beta 1. Use the Xcode 11.3.1 for running on real devices until the next beta of Xcode will be released.

0
On

Are you using a non-developer Apple ID to install the app on your phone? It looks like iOS 13.3.1 has broken apps installed with free Apple IDs, but only if they contain embedded frameworks. If it's possible to link all your dependencies as static libraries rather than frameworks (for example, if you're using Cocoapods you can remove use_frameworks! from your Podfile), that should fix the issue for now.

4
On

As was mentioned above:

Apple blocked utilizing external frameworks on free accounts with 13.3.1 upgrade.

So use developer account with active subscription or use static libraries.

Solution for Cocoapods - use use_modular_headers!

0
On

I faced same problem. power of use_modular_headers! to avoid the crash and below code working for me.

# Uncomment the next line to define a global platform for your project
#platform :ios, '10.0'

target 'YourApp' do

   use_modular_headers!
  # Pods for YourApp

   pod 'Kingfisher', '~> 5.0'
   pod 'GoogleMaps'
   pod 'GooglePlaces'
   pod 'Firebase/Analytics'

end
2
On

Looks like whe only way to avoid error on free account is use ios 13.3, because even in iOS 13.4 beta apple didn't fix it. Using use_modular_headers! is not working for Firebase.

1
On

I had the same problem after updating my iPhone to iOS 13.3.1. The fix that has worked for me: In the Podfile remove use_frameworks! and add ,:modular_headers => true after each pod. Close xcode, update pods and rebuild.

My full Podfile looks like this:

target 'HeatingClient' do
  # use_frameworks!

  pod 'RxSwift',:modular_headers => true
  pod 'RxCocoa',:modular_headers => true

end
2
On

I was using apple free account, switched to apple paid account and it worked in iOS 13.3.1

5
On

This issue is specific to iOS 13.3.1 devices with free dev account, i was struggling with it for 4 days and got the solution.

  1. Uninstall Pods from your project folder, use terminal:

    sudo gem install cocoapods-deintegrate cocoapods-clean pod deintegrate pod clean rm Podfile

  2. Initialize pods again in project, terminal: pod init

  3. In Podfile change this line:

    target 'exampleproject' do
      # Comment the next line if you don't want to use dynamic frameworks
        use_frameworks!
    

    to this lines:

    target 'exampleproject' do
      # Comment the next line if you don't want to use dynamic frameworks
      # use_frameworks!
      use_modular_headers!
    
  4. Install Pods again in terminal: pod install

  5. Open project by file .xcworkspace and do Product > Clean Build Folder (Command+Shift+K)

  6. Run and build with free developer account on your iOS 13.3.1 device.

2
On

the issue is with iOS 13.3.1 and free developer accounts . the issue is fixed on latest iOS 13.4 beta I confirm it. for now you can use

use_modular_headers!

instead of

use_frameworks!

in project Podfile