-
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
Undefined symbol: _OBJC_CLASS_$_GULAppEnvironmentUtil #8137
Comments
I found a few problems with this issue:
|
Thanks for reporting, @khoogheem. Can you share the detailed steps reproducing the issue? Also, a |
Pod updated project all Firebase were set to 8.0.0 |
Can you share your Podfile.lock? |
Also, are you building with |
Correct
Sent from your iPhone
… On May 24, 2021, at 5:49 PM, Morgan Chen ***@***.***> wrote:
Also, are you building with use_frameworks! and not using :linkage => :static?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
this is what we add in:
|
Can you share the full build log output? It's likely this is occurring in a submodule of your app (i.e. one of your dependencies) and not the app itself. |
|
if you want the lock file send me an email that I can sent it too.. vs posting here |
Ok.. if I use:
Then it works... which is odd as the only thing I see different between the two locks is core and analytics are swapped |
You should be able to fix this temporarily by going to your A more permanent fix may need to come from CocoaPods or Firebase; some further investigation is required. |
Same
|
Had the same issue, XCode -> Product -> Clean Build Folder fixed it. |
Marking as needs-info for a repro case from a clean build environment |
I added this but still have the crashlytics error (even after a clean and fresh build). If I remove Crashlytics, things compile properly. I did try the temporary fix you mentioned earlier about adding GoogleUtilities to the Link Binary with Libraries, but still saw the same error. Overall, at this point I'm just excluding it. |
@paulb777 similar linker error in firebase/FirebaseUI-iOS#969. |
Thanks @morganchen12. I'll take a look in the next day or two |
The FirebaseUI issue turns out to be a test infrastructure issue specific to FirebaseUI. See the firebase/FirebaseUI-iOS#969 for details. So we're still looking for a reproducible example. |
Was able to remove the issue by updating my pod file from this:
To this:
After running pod install, I cleaned my build folder, then deleted derived data for the app. |
Thanks for the note @mentalGrowthNick. I do have Performance in my Podfile but I still get this issue even after doing all of the steps you mentioned. When I did the pod update I noticed that many of the pods I have updated to 8.2.0, but even with the new changes and everything, this problem persists. As of today, I'm just not including Crashlytics at all and it's building. I would like to get it added but can't seem to get it working at the moment. |
@billdevoe can you share your project? |
Hi @morganchen12 - I don't have anything simple that I could share at this point (this is a workspace/project for a published game). I will try to see if I can replicate the issue with a project that I could share. |
So I just created a new project, added the Pods (shown below) and then tried to build the workspace - same error. This is about as basic as it gets. Podfile (removed the commented lines as they hork the formatting):
Podfile.lock:
I'm wondering at this point if it's something about Objective-C or the target (iOS 12.1) or something else. I did have to do a LOT of updates to get gems working properly, but if I put the Crashlytics pod into the Podfile, I get the error. |
@billdevoe I tried reproducing this build failure with a very similar Podfile but was unable to do so (see the attached sample project). I'm using Xcode 12.3, though that shouldn't be a factor in this issue. |
Hi @morganchen12 - I built the example project you posted and it works (when I correctly remember to change the build target to the iOS version). So it's not completely FUBAR on my machine, just with most of the basic things I'm doing. I'll keep poking around to see what differences exist between the two things. This is the project I made that doesn't build properly for me. |
Thanks for providing the example. The issue is clear now and fixed in #8308. The Crashlytics podspec was not defining one of its dependencies. We do not typically see this issue because it is only exposed by an unusual Podfile. Putting |
Thanks @paulb777 - I used someone's example of a Podfile to create mine. I guess I didn't realize it was in the target. BUT - moving it out of the target section of the Podfile DOES fix the issue. Happy I was able to help you identify a bug and fix it. :D Thanks for all the help, everyone. Very happy that things are working now. Much appreciated. |
So is the solution to move
out of the loop?
|
Is this as intended? |
Hmm, it looks like the fix missed 8.3.0. Sorry about that. It is staged for 8.4.0 - https://github.com/firebase/SpecsStaging/blob/master/FirebaseCrashlytics/8.4.0/FirebaseCrashlytics.podspec.json |
When will it be deployed to public specs ? |
The 8.4.0 CocoaPods versions published today. |
I just noticed this issue is still in our top ten search traffic. If you're still seeing this with releases after 8.4.0, please open another issue. |
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Undefined symbol: OBJC_CLASS$_GULAppEnvironmentUtil
Steps to reproduce:
Build using 8.0.0
The text was updated successfully, but these errors were encountered: