dyld: Library not loaded - iOS 13.3.1 and embedded Mapbox.framework

[julianrex]

We are tracking an issue with iOS 13.3.1, that results in the following error in the Xcode console, when running on an iOS device:

dyld: Library not loaded: @rpath/Mapbox.framework/Mapbox [...] Reason: no suitable image found

This does not affect apps already on the App Store or on your users' devices.

Please ensure that you are enrolled in a paid developer account. If using a business account, double check you are not using the team annotated with (Personal Team).

Alternatively, you can build-and-run with an iOS simulator, until Apple releases an update.

This is being reported elsewhere:

• https://forums.developer.apple.com/message/404653
• iOS 13.3.1 dyld: Library not loaded Alamofire/Alamofire#3051
• Running new app on actual iOS (13.3.1) device crashes on startup: code signature invalid for "path/to/Flutter.framework/Flutter" flutter/flutter#49504

For Cocoapods users: you may have read that remove use_frameworks! will help - in our case this won't as we do not (currently) provide a static framework or support building from source; the issue is with embedded dynamic frameworks.

Reported as FB7563776.

[julianrex]

This appears to happen for the recent iOS 13.4 beta.

[Fatehkhann]

I can't get it working. It's happening with all CocoaPods libs.

[SiarheiFedartsou]

It seems to be a new Apple restriction: https://stackoverflow.com/questions/60096258/library-not-loaded-rpath-fblpromises-framework-fblpromises-ios-13-3-1

[jamesburriss]

I am a paid apple developer and still having this issue?

[zhuansun0502]

OK I have struggled for a while and I found 2 ways to fix this.

1. Sign up for paid Apple Developer account($119CA/year). Some people say it doesnt work. Here's the answer:
   RENEW YOUR CERTIFICATE!
   Go to your keychain access, generate a new certificate request then follow the instructions on your paid account page to download a new certificate. When it gets renewed, you are good to go.
   @jamesburriss I am guessing you are using 2 different accounts for you development. So you are not getting auto-renewed

[zhuansun0502]

2. use_modular_headers!
   If you have done enough research, you know what I am talking about. The reason I am not using it is because I hate having tons of warning of "not able to update" and "unable to render" sort of things in my Xcode.
   Let me know if this helped

[jamesburriss]

The issue was with my certificates. Thank you very much I was new to all rbis James

…

On 22 Feb 2020, at 00:57, zhuansun0502 ***@***.***> wrote:  OK I have struggled a while and I found out 2 ways of fixing this. Sign up for paid Apple Developer account($119CA/year). Some people say it doesnt work. Here's the answer: RENEW YOUR CERTIFICATE! Go to your keychain access, generate a new certificate request then follow the instructions on your paid account page to download a new certificate. When it gets renewed, you are good to go. @jamesburriss — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[julianrex]

Noting that our Feedback to Apple was updated with

Recent Similar Reports: More than 10
Resolution: Potential fix identified - For a future OS update.

We will close this issue once we can prove it has been fixed in by an OS update.

[julianrex]

Closing as solved in iOS 13.4 (as noted elsewhere).