Alamofire: iOS 13.3.1 dyld: Library not loaded

[Wasa22]

I'm getting this error when trying to run my app with Alamofire 5.0.0-rc3:

dyld: Library not loaded: @rpath/Alamofire.framework/Alamofire
Referenced from: /private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/SupremeYou
Reason: no suitable image found. Did find:
/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire: code signature invalid for '/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire'

/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire: stat() failed with errno=25
/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire: code signature invalid for '/private/var/containers/Bundle/Application/CC8FF01F-CB03-4D92-ADDE-8B458EDF3D74/SupremeYou.app/Frameworks/Alamofire.framework/Alamofire'

I've been tested my app on an iPhone 11 Pro 13.3 and it was working fine until I decided to update the phone. So I update the iPhone 11 to the 13.3.1 version, and the error started to appear.

it works fine on an iPhone 8 Plus with iOS version 13.3.

Also it doesn't work on an iPhone 6s with iOS 13.3.1.

[jshier]

Have you rebuilt using Xcode 11.3.1 and distributed a new build to the device?

It's unlikely there's anything Alamofire can do here, but I'll keep this issue open until we see some sort of conclusion as to cause.

[Wasa22]

Yes, I rebuilt it with Xcode 11.3.1 but keeps crashing. I also tried a clean install but nothing, throws the same error.

Looks like Apple made something in the last iOS version, everything works fine on 13.3, it only happens on 13.3.1.

Maybe it's something with the dynamic frameworks; a workaround I found in CocoaPods is comment the use_frameworks! line in the Podfile, do a pod update, pod install, clean and run. And now I can run my app again on my 13.3.1 devices.

[rfcj]

I also have the same error, but when I comment use fameworks! i have problems with other pods

[Wasa22]

@rfcj I forgot to mention that I added use_modular_headers!. In my case, I'm using Realm and that pod keep throwing me error until I added the line I said.

Try that, maybe it will help with your pods.

[rileytestut]

Are you using a non-developer Apple ID to install the app to 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.

[rfcj]

rileyestut, Yes, for now I am using a non-developer Apple-ID. And if I remove the use_frameworks! then I have problems with FirebaseAuth. And yes the problem occurs in others frameworks as i see now.

[rfcj]

Wasa22, thanks, work with use_modular_headers!.

[honga]

@rileytestut removing use_frameworks! and using use_modular_headers! didn't work for my various Firebase pods. But does this mean swapping to a paid developer ID will resolve this error?

[vicajilau]

I have the same problem

[ronalson]

@rileytestut Can you point me to any resource stating this fact? I'm fighting with this issue for almost 3 days already (on a Nativescript project) and your explanation is the only one that actually make sense (sadly, but it does).

[rileytestut]

@ronalson Unfortunately all this is just coming from my own investigations; I can't find any official documentation on the matter. I've been trying to discover the root cause of this since it's directly impacting my own project as well, but still not sure if this is an intentional decision or just a bug.

FWIW, this same issue was present with the first few betas of iOS 13.2 as well, but was "fixed" by the GM so I assumed it was just a bug back then. However, now that it was also in the iOS 13.3.1 betas as well as GM, I'm not so sure 😐

[rileytestut]

@honga Yes, using a paid developer Apple ID should fix the issue AFAIK

[Wasa22]

Yeah it looks like the problem is the free Apple ID provisional profile.

Another people are mentioning this behavior like here:
https://github.com/ionic-team/capacitor/issues/2383

And they said that the issue is solved with a paid developer Apple ID.

[zackshap]

removing use_frameworks! worked for me. I didn't need use_modular_headers!

[marcocanestrari]

Same problem with Realm, removing use_frameworks! and adding use_modular_headers! worked

[sebastianhoratiu]

What fixed this issue in my case was to delete the Apple Development profile from my device and then let Xcode install it again when I ran the app on the device.

General > Device Management > Apple Development ... > tap on it then tap on Delete App. Then when you run again the app one your device the profile will be installed again and you'll be asked to Trust it again.

[kpostekk]

In my case it also required to reinstall provisioning profiles on my device

[orakay]

rileyestut, Yes, for now I am using a non-developer Apple-ID. And if I remove the use_frameworks! then I have problems with FirebaseAuth. And yes the problem occurs in others frameworks as i see now.

I am using SQLite.swift framework with free developer account and experiencing the same trouble using iOS 13.3.1. Apple seems to be preventing unpaid accounts use frameworks in their applications in iOS 13.3.1.

None of the workarounds worked for me by the way...

[jasval]

Are you using a non-developer Apple ID to install the app to 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.

Thank you so much Riley! I was about to smash my keyboard in frustration haha.

[oem66]

I had same issue with Alamofire, and solved it by removing use_frameworks! from pod file and adding use_modular_headers! then in console pod deintegrate, pod update and pod install
Now everything works fine.

[ahumeb]

Commenting out use_frameworks and adding use_modular_headers! to the Pod file. Then going to console pod update and pod install; after that Clean Build Folder and running made the trick! Thank you!

[emilylam]

Can confirm; it has to do with a free account. Paid for an account [had to call up Apple to get them to process my order quicker] and my app is back up and running.

Disclaimer: my app has nothing to do with Alamofire but I came across this thread when looking for answers to my issues.

[fobass]

Getting seem problem but I don't want paid account yet any other solutions

[sebastianhoratiu]

It worked for me after a pods update and deleted the developer profile from the iPhone(General > Management...)

[EscolarProgramming]

I had same issue with Alamofire, and solved it by removing use_frameworks! from pod file and adding use_modular_headers! then in console pod deintegrate, pod update and pod install
Now everything works fine.

That was the solution which worked for me in the project without Alamofire, thank you!
Unfortunately, in another project where I use Alamofire I get the linker error "framework not found Alamofire". It seems like it needs the use_framwork! ... a doom loop

[hamed8080]

waste 2 days for searching and found this ! unbelievable apple 😑

[javierCueto]

@rfcj I forgot to mention that I added use_modular_headers!. In my case, I'm using Realm and that pod keep throwing me error until I added the line I said.

Try that, maybe it will help with your pods.

That works, you saved my life 🥳

[liudasbar]

I had same issue with Alamofire, and solved it by removing use_frameworks! from pod file and adding use_modular_headers! then in console pod deintegrate, pod update and pod install
Now everything works fine.

This has worked for me!

[BossOz]

@rileytestut removing use_frameworks! and using use_modular_headers! didn't work for my various Firebase pods. But does this mean swapping to a paid developer ID will resolve this error?

I'm figuring out the same error and, after have payed the Apple Developer account, nothing change...

[jshier]

I would suggest everyone who is hitting this issue report a bug to Apple using the Feedback Assistant so that it can get fixed sooner rather than later. Additionally, anyone needing addition help fixing it should use StackOverflow or the Apple Developer Forums. Alamofire's GitHub issues is not the right place, if only because the audience here is very limited.

[alperen23230]

I have a issue with non-paid Apple Developer account. use_modular_headers! solved my problem.

[tech234a]

Does anyone know if this was fixed in the iOS 13.4 beta?

[ayafuji]

removing use_frameworks! worked for me. I didn't need use_modular_headers!

I had a this issue and fixed it. I would like to add one process. pod update if you use pod after changing above line.

thanks to avoid spending time.

[BartmanEH]

Does anyone know if this was fixed in the iOS 13.4 beta?

not according to this.

[BenQF]

I had this problem, but it was due to the fact that I had Alamofire and CodableAlamofire in the project. CodableAlamofire on its own brings over Alamofire, so for some reason it was causing this same issue. Removed Alamofire from the Podfile and just kept CodableAlamofire and worked like a charm.

[guilhermeRangel]

Hi the problem is in iOS version 13.1.3 eu tested in device different e is ok

[CarlosP10]

@rfcj I forgot to mention that I added use_modular_headers!. In my case, I'm using Realm and that pod keep throwing me error until I added the line I said.

Try that, maybe it will help with your pods.

I'm getting some issues with realm and i do everything you mentioned, delete use_framworks! line and add use_modular_headers! clean and rebuild and now it shows me Realm need framework @Wasa22 you dont have that problem?

[liudasbar]

Could it be this thing?

"Apple blocked utilizing external frameworks on free accounts with 13.3.1 upgrade. Try downgrading to 13.3."

https://stackoverflow.com/a/60211703/8574785

[ivrylobs]

Yeah it looks like the problem is the free Apple ID provisional profile.

Another people are mentioning this behavior like here:
ionic-team/capacitor#2383

And they said that the issue is solved with a paid developer Apple ID.

Apple just wants our money to run our apps lol.

[iOSayedAhmed]

I comment use_frameworks!
then run my project on iphone 8plus version 13.3.1 it's working
Thanks ^^

[sean9keenan]

This issue seems to be fixed on the latest beta for iOS 13.4 🎉
(the one released today)

[rileytestut]

Can confirm, apps containing embedded frameworks installed with free Apple IDs are now working for me on iOS 13.4 beta 3 😄 Hopefully it stays fixed for GM!

[TKisely]

The beta solved for me as well.

[RachelGilbert95]

I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my iPhone I got this error "Could not locate device support files. This iPhone X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which may not be supported by this version of Xcode. An updated version of Xcode may be found on the App Store or at developer.apple.com."

[ivrylobs]

You should update you Xcode to the version that support iOS beta version

On Sun, 1 Mar 2563 at 23:32 Rachel [e-mail] wrote:

I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my
iPhone I got this error "Could not locate device support files. This iPhone
X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which
may not be supported by this version of Xcode. An updated version of Xcode
may be found on the App Store or at developer.apple.com."

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Alamofire/Alamofire/issues/3051?email_source=notifications&email_token=ADKYITNMR7SSDV7STLVBYO3RFKEZPA5CNFSM4KM5O4VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDZTQ#issuecomment-593116366,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADKYITLOMMN6WB7TITWVS5DRFKEZPANCNFSM4KM5O4VA
.

[RachelGilbert95]

You should update you Xcode to the version that support iOS beta version
…
On Sun, 1 Mar 2563 at 23:32 Rachel @.*> wrote: I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my iPhone I got this error "Could not locate device support files. This iPhone X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which may not be supported by this version of Xcode. An updated version of Xcode may be found on the App Store or at developer.apple.com." — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3051?email_source=notifications&email_token=ADKYITNMR7SSDV7STLVBYO3RFKEZPA5CNFSM4KM5O4VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDZTQ#issuecomment-593116366>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKYITLOMMN6WB7TITWVS5DRFKEZPANCNFSM4KM5O4VA .

It says Xcodes up to date.

[projecttryone]

I am having the same issue with my app while deploying it into iPad .. I am using cocoa and Mqtt to connect my app to my pi . it works on the virtual iPad . is it something related with privacy guys ? I mean the iPad is not letting use the Mqtt server or something >>?

[ivrylobs]

You should update you Xcode to the version that support iOS beta version
…
On Sun, 1 Mar 2563 at 23:32 Rachel _@_.*> wrote: I updated my iPhone to iOS 13.4 beta 3 but when I went to run my app on my iPhone I got this error "Could not locate device support files. This iPhone X (Model A1865, A1901, A1902, A1903) is running iOS 13.4 (17E5241d), which may not be supported by this version of Xcode. An updated version of Xcode may be found on the App Store or at developer.apple.com." — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3051?email_source=notifications&email_token=ADKYITNMR7SSDV7STLVBYO3RFKEZPA5CNFSM4KM5O4VKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENNDZTQ#issuecomment-593116366>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADKYITLOMMN6WB7TITWVS5DRFKEZPANCNFSM4KM5O4VA .

It says Xcodes up to date.

What's your Xcode version?
for newest beta version is 11.4 beta 2
Did you enroll apple developer program?

[jshier]

It seems this issue has run its course and is fixed in the 13.4 betas. I'm going to leave it open until 13.4 is officially released (probably sometime in March) and see if it's still fixed. However, I'm locking it for now as it's getting quite off topic. Anyone needing other support is encouraged to search online or move to StackOverflow.

[jshier]

Now that Xcode 11.4 and iOS 13.4 has shipped, can anyone confirm that the fix for this issue made it into the release?

[jjlawren]

It's finally working again on the new Xcode and iOS releases.

[anton9812]

Yes i can confirm it is working right now. You dont understand how relieved i am feeling..

[jshier]

Great! Thanks for the help everyone, I'm happy to finally close this issue.

[ooanishoo]

Are you using a non-developer Apple ID to install the app to 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.

Hi when I comment out use_frameworks! from your Podfile, I get vibration/vibration-Swift.h file not found. Please help !
Refer to this for the error log: https://github.com/benjamindean/flutter_vibration/issues/1

[jshier]

Sorry, this thread isn't for long term support.