-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
[iOS] FirebaseCore/Firebasecore.h not found #92
Comments
I had the same issue with the messaging subsystem, see #91 |
Hello, thanks for your answer, I saw your issue and tried to do the same. I was also using messaging only, so I tried to compile the QtFirebaseExample project with all the components, and I still got the same error. The error came from the iOS SDK version. I had the 5.8.0, and i downloaded the 5.3.0 instead, and then only it worked. Download link |
The firebase cpp sdk version I use is v5.3.0. If you try to build all components with newer version of the sdk you need to make changes to the linked frameworks in qtfirebase_target.pri. |
Yes I have the same version of cpp SDK, the link in the sh scripts is a download link from firebase where they provide the last version of their SDK, so it changes evey month I guess. |
Hmm... They must've moved something around in the latest versions then. I'm hoping to get some more time for brushing things up in the coming weeks |
|
It seems that Google has changed the naming of frameworks again with the C++ SDK v5.3.0 release. These two frameworks are now needed to build Analytics (and probably Firebase core if you aren't including the Analytics module): And these two no longer exist: I've only tested the Analytics and Messaging modules for changes, so there could be more changes needed to fix other modules. The latest Firebase iOS SDK is v5.9.0 now, so updating it is also advisable if you are using the latest C++ SDK v5.3.0. |
I think that this was closed by 86f539a. However, it seems that FCM may not require Analytics/Core any longer, so this might be a requirement that QtFirebase can drop. |
Has anyone been able to resolve this problem without resorting to modifying the Google Firebase code? With Google Firebase SDK 1.6.0, I have only been able to work around this issue by modifying the following files from the iOS Frameworks:
In Firebase.h, I need to change: In FIRConfiguration.h, I need to change: And then I need to add the following to INCLUDEPATH in qtfirebase_target.pri: Does anyone know why qmake isn't finding the FirebaseCore framework headers? According to the instructions at https://doc.qt.io/qt-5/qmake-platform-notes.html, I tried adding the following to qtfirebase_target.pri:
That doesn't help. Any ideas? |
It's super weird - and I haven't been able to track it down as of this writing |
I encountered this issue in my project. Make sure your -F flags are properly set up, for example Firebase iOS SDK 6.14 changed |
Could you please serve a working ios example? i did it (one year) before, but after last changes i am working for three days and lost my way. i really want to stay within Qt but it gets harder to maintain. |
I will give this problem one more shot once I get to work on Monday. I cannot promise anything as XCode builds are very very slow on our Mac Mini. |
Should be fixed with #152 |
Thanks @Sharm - it's in master now |
Hello, and first of all thank you very much for all the huge work you put into this plugin !
I made it work perfectly with Android, but I have a problem under iOS.
I followed all of your steps. After downloading the Firebase iOS SDK, I unzip it and put it under the src/ios folder, (location of the sh script), this is the 5.8.0 of the SDK. But when building, I have the following error :
In file included from ..../src/ios/AppDelegate.mm:4 FirebaseCore/FirebaseCore.h file not found #import <FirebaseCore/FirebaseCore.h>
So I checked in the folder of the firebase SDK, and there is no FirebaseCore folder, maybe this come from the version of the iOS SDK ? I couldn't find zipped previous versions
Thank in advance for your help !
The text was updated successfully, but these errors were encountered: