-
Notifications
You must be signed in to change notification settings - Fork 46
[Bug] Xcode Build Failure Undefined Symbol firebase::firestore::nanopb::SharedMessage<firebase::firestore::_google_firestore_v1_Value> #975
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
Comments
Thank you for the report. I will look into this as soon as possible. |
We are using Unity 2022.3.10f1 with Firebase 11.8.0 and experiencing the same issue. |
Same here |
Hi We are facing the same issue as below: We received an email from Apple requesting builds using the iOS 17 SDK or later (due date mid-April), so we proceeded accordingly. However, after upgrading to MacOS Sonoma 14.4 and Xcode 15.3, we encountered several crashes on devices running iOS 17.3 and 17.4. To address this issue, we upgraded to Firebase SDK version 11.8.0, previously we were using version 11.6.0. Initially, this resolved the issue, and we were able to successfully build for a couple of days. However, today, when attempting to create another build, we encountered the attached errors and are unable to proceed further with the build process. We attempted to downgrade to version 11.7.0, but encountered the same error with that version as well. Would you please give advice or help in getting out of this? it impact our business. |
Have you all tried the fix outlined in my original post? It fixed it for us, and I'm pretty sure it will fix it for you all as well, maybe with a few tweaks based on which packages you use |
@shniqq thanks for your quick reply |
@shniqq Hi I tried this solution. Didn't help. I tried making all to 10.22.0, and also making all to 10.23.0. But same error in both cases attached our Podfile.lock cc @palashSpoilz |
I've detailed the problem, and potential workarounds here: #974 (comment) |
hey then in your terminal cd into the folder then do pod install --verbose as the installation happens notice the firebase dependencies now you can either use the script provided and update the firebase dependencies list with the the dependencies you noted above which on export from unity will add these dependencies explicitly in the podfile thats generated. or manually after the unity export you can open up the pod file and you can type in the pod commands yourself for the noted dependencies with 22 version. |
Same here |
Please share link of the post |
@mianumar I've described a workaround here: #974 (comment) |
As commented in #974 (comment), there is a new hotfix release out that should address this. Will close this issue, and thanks for bringing it to our attention. |
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
Since 19th March we are getting the following Xcode linker error:
Given there were issues with resolved dependencies not long ago caused by some stealthy behind the scenes dependency update see here, plus there is some Firestore "Adding unlinked" stuff going on in Firebase iOS SDK, I assume this has something to do with it.
I noticed there are some dependencies pulled in that are not explicitly specified by us or any SDK, so they must be pulled in as dependency of one of the native iOS Firebase SDKs, see this excerpt from
pod install
:Notice the 10.23.0 versions.
Steps to reproduce:
100% failure rate when having Firebase SDK 11.8.0 in the project.
Fix
We were able to fix it (similar to the last issue linked above) by explicitly specifying the version of the dependencies further down the chain using this post processor:
Note, your affected dependencies might differ, just have a look at the
pod install
logs.The text was updated successfully, but these errors were encountered: