-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Trying to use the source pod integration #702
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
We've been making a lot of changes in this area lately so it's possible this has been broken. Was this working previously or are you trying for the first time? Meanwhile I'll look at reproducing this. Our own development runs in-repo which may mean that our HEADER_SEARCH_PATHS are broken. |
The header paths weren't broken but we weren't properly including the abseil sources in the podspec. This is a start on a PR to fix those: However, we're still stuck on this because it appears that the binary release doesn't include all the private headers required to make this work:
However, if you change your Podfile to also include FirebaseCore from source this works.
I'll get the PR in so that you can pull Firestore without the branch and we'll have to look into how to change the release process so that the necessary private headers are included (if that's at all possible). |
Okay, discussing internally, it's clear that the FirebaseCore we publish won't include these headers. If you want to use any components from source you'll need to get FirestoreCore from source too. Once #704 lands you should be good to go. |
Submitted. The podspec changes are now in master and you should be able to build from source. |
I am trying to use the source pod integration but once I do and try to compile I get an error.
So here are my pods:
Now I can see the sources that have replaced the binary framework.
But when I try to compile it, I get the following error:
The text was updated successfully, but these errors were encountered: