-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linking FirebaseInstallation fails with lld #10071
Comments
I found a few problems with this issue:
|
Thanks for the report. This may be a CocoaPods issue with the Promises dependency. How serious is the issue for you? Is it more than an annoyance in the build log? |
@paulb777 The issue is an error using Does the zipped distribution get built from the podspecs? Looks like the PromisesObjC |
Yes, the zip distribution is created from the podspecs. It looks like our build tooling is trying to sort out the module name/pod name conflation at https://github.com/firebase/firebase-ios-sdk/blob/master/ReleaseTooling/Sources/ZipBuilder/FrameworkBuilder.swift#L291 cc: @ykjchen |
@sebastianv1 Does renaming |
@paulb777 I have not tried this yet, currently we are able to workaround it by using an empty FBLPromises dummy framework that we include the link list. Would it help if I tried? |
@sebastianv1 Yes. It's essentially what the fix in #10073 does and I'd like to confirm it works for your use case. |
I believe that #10073 should fix the issue and it will be part of the next 9.5.0 release. |
[REQUIRED] Step 1: Describe your environment
Zip file
(select one)All
[REQUIRED] Step 2: Describe the problem
When linking our app using
lld
, we receive the following error:We discovered that this is coming from
FirebaseInstallation
whoseLC_LINKER_OPTIONS
includesFBLPromises
as a load commandIt appears that
FBLPromises
was renamed toPromisesObjC
and is a dependency ofFirebaseInstallation
& included in the zipped release of frameworks. We do linkPromisesObjC
into our bundle, but my guess is that the distribution step still links against the oldFBLPromises
name?This doesn't throw an error in
ld
though since it'll ignore invalid frameworks included by theLC_LINKER_OPTIONS
flag (llvm/llvm-project#56939).Steps to reproduce:
Link an app using
lld
againstFirebaseInstallation
+ dependencies.What happened? How can we make the problem occur?
error: framework not found for -framework FBLPromises
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
The text was updated successfully, but these errors were encountered: