Error Dyld: Library Not Loaded: @Rpath/Gtmsessionfetcher.Framework/Gtmsessionfetcher - Code Signing Error

Error dyld: Library not loaded: @rpath/GTMSessionFetcher.framework/GTMSessionFetcher - Code signing error

I have been facing the same problem... It got fixed by adding:

In you podfile:

use_modular_headers!

instead of

use_frameworks!

Good luck! I hope this works for you!

Xcode error - dyld: Library not loaded won't resolve

Problem Solved
The problem with nothing to do with something I did or could’ve controlled, needless to say that I recoded the whole app from scratch for nothing, even though I like it a whole lot better now.

The problem was the version of iOS I was running. I had used a Beta version of iOS (iOS 13.3 Beta 3) and this had for some reason been conflicting with the DeviceSupport folder I added to Xcode and wasn’t working properly.

If you are here because you are having the same issue, follow the following steps!

Method 1: Clean your build
- Open the damaged project
- CMD + SHIFT + K
- CMD + B

Method 2: Reset Keychain to Default
*• THIS WILL RESET YOUR KEYCHAIN •
- Open Keychain Access
- Select Keychain Access > Preferences
- Select General
- Select Reset My Default Keychain

Method 3: Reset Certificates on Device
- Open Xcode
- Connect affected iDevice
- Press CMD + Shift + 2
- Right Click Device
- Select View Provisioning Profiles
- Delete any profiles that pertain to your app

Method 4: Reinstall the latest supported version of iOS
If you haven’t installed any beta versions of iOS, you can ignore this
- Back up your device in case anything goes wrong!
- Go download the latest stage version of iOS that in the form of IPSW and is signed
- Connect iDevice to computer
- Select Restore while pressing (SHIFT/CMD) and then select the downloaded IPSW file and wait.

dyld: Library not loaded: @rpath/ ... Reason: no suitable image found. updated device to latest update 13.3.1

If you're using Cocoapods you can remove or comment by # use_frameworks! from your Podfile and reinstall it, that should fix the issue for now. dont forget to clean build folder before you run the app on update 13.3.1 device.



Related Topics



Leave a reply



Submit