-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Updating to 10.23.0 results in 'FirebaseCrashlytics/FirebaseCrashlytics-Swift.h' file not found #12611
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @OscarFyl, I tried to reproduce the issue, but I'm able to successfully run the app. Could you provide your |
Same error as in #12605. Need more details to know if it's the same root cause. |
Podfile.txt |
Hey @OscarFyl |
Hello, I have the same problem. But since the version 10.22.1 everything worked well. Did something change ? |
I experienced similar building errors after updating Firebase SDK in the past with static linking, as others recommends you have to switch to The following solution is working for me well, with keeping all my other dependencies as static libraries (starting the podfile specification still with
|
Hey @paul-lavoine We added a swift module in Crashlytics for 10.23.0 #12410. This is related to change in release note for 10.23.0 https://firebase.google.com/support/release-notes/ios#crashlytics |
My project also got hit with this issue. 30+ external libraries, 10+ spm packages, mix of ObjectiveC + Swift codebase. After applying the suggested fixes above, Xcode choke on more errors... 🤮 reverting back to |
My project also encountered this problem. I saw that this has been closed, but how to solve it? |
Podfiles should include either |
Hi @paulb777, |
Hey @paulb777 , after adding use_frameworks! in the Podfile caused many errors related to "Module map 'xxxx' not found" when building the unit tests. What can be the workaround here? Thks! |
Thanks, option 1 doesn't work, with option 2 I can |
Reopening to investigate making a less-disruptive migration to the Swift-implementations. |
What version has this fix? |
@tomerh2001, this fix has been checked in and will be released in Firebase 10.24 (due out week of April 9). |
Oh I see. This bug is currently preventing us from compiling our app, any temp workarounds for now? We're using:
If I understand correctly you are the not the maintainers of these, but they do use this package under the hood - so maybe a version that previously worked (and I'll find the matching |
Downgrading |
Description
API Proposal
No response
Firebase Product(s)
Crashlytics
The text was updated successfully, but these errors were encountered: