111

I have a slight issue when build my Xcode project, get tones of warning after update pod. It looks like this

enter image description here

Already search the whole site here but still no luck. it doesn't affect the project but it is quite annoying. Anyone could help?

Alexander Huang
  • 1,345
  • 2
  • 11
  • 16

5 Answers5

86

It probably means their binary file has non-aligned pointer when they compile their code. In those cases the alignment basically defaults to 1 byte and hypothetically might impact performance. After updating to Xcode 8.3 public release I am still seeing this error, so Google might need to compile their static library with different settings to make it go away.

tzm41
  • 976
  • 7
  • 11
  • 49
    That's correct, we're aware of the warnings being generated, and we're working on an update to remove the warnings. – Rizwan Sattar Mar 30 '17 at 21:01
  • 3
    @RizwanSattar What is the status of the fix? – cbartel Apr 10 '17 at 15:09
  • 1
    The protobuf warnings should be gone as they've updated their pod. If you run pod update, most of the warnings should be gone. We're preparing a release of firebase tha should get rid of the remainder of the warnings. – Rizwan Sattar Apr 12 '17 at 01:11
  • 1
    @RizwanSattar running pod update does not remove any of the warnings currently – jakedunc Apr 12 '17 at 12:38
  • @RizwanSattar The new updates to FirebaseCore seems to be breaking things. When running pod update, it installs FirebaseCore 3.6.0 but removes Protobuf, and installs older versions of Firebase, FirebaseAnalytics, FirebaseInstanceID and FirebaseMessaging. As a result I am getting compilation errors due to 126 duplicate symbols for architecture x86_64 between FirebaseAnalytics and FirebaseCore. Is there new update coming to the Firebase pod itself soon? – tzm41 Apr 12 '17 at 19:16
  • 1
    Firebase 3.16.0 is out and fixes these issues. Thanks! – tzm41 Apr 13 '17 at 01:07
  • @RizwanSattar Firebase 3.16.0 installed and does not make any difference to the warnings generated. ld: warning: Linker asked to preserve internal global: '__block_descriptor_tmp' ld: warning: Linker asked to preserve internal global: '__block_literal_global' ld: warning: Linker asked to preserve internal global: 'sharedInstance.sharedInstance' – PKCLsoft Apr 16 '17 at 08:31
29

Got this response from firebase support:

This is a known issue with Xcode 8.3 beta, so it might be a beta thing and Xcode being extra verbose. It works well though with 8.2.1 so I recommend temporarily use it to avoid the warnings or ignore the warnings on 8.3 beta if it does not affect your app.

kball
  • 4,923
  • 3
  • 29
  • 31
  • 19
    It's a problem in xcode 8.3 release. How embarrassing for google. Firebase already causes notification warnings when uploading your app. I'm going to ditch it. I'm sick of them not having their act together. – cvb Mar 28 '17 at 00:46
  • 5
    Pretty ridiculous. It's extra frustrating because just using the Google SignIn pod automatically includes all the (unwanted) Firebase stuff - wish I could ditch it too! – cuomo456 Mar 28 '17 at 02:18
  • Yes just now updated my Xcode there are many warning about that google and firanalytics. Is there any release about that pods? – iamburak Mar 28 '17 at 10:12
  • 1
    I'm not sure if the problem is Google-specific; I am getting the same warnings when using the D compiler, which (as far as I can tell) has nothing to do with Firebase. – Hans Nowak Mar 29 '17 at 01:37
  • Some comment from Apple and/or Google about the issue would be, fair. – Jonny Mar 29 '17 at 10:10
  • Create a ticket at firebase. I did. – Michal Mar 29 '17 at 11:48
  • 3
    @michal Link to your ticket so we can star it instead of creating duplicates. – riper Mar 29 '17 at 12:04
  • 26
    Hey folks, just wanted to let you know that the Firebase team is aware of the warnings generated in Xcode 8.3 and we're working to remove them. This comes down to a compilation issue, and should not cause any problems in your code, though it's still ugly, and we shouldn't be generating any warnings. – Rizwan Sattar Mar 30 '17 at 21:00
  • Happens to me now with 33 warning. – Roei Nadam Apr 02 '17 at 16:30
  • I have 39 warnings in my project because of this, this makes my OCD unhappy. Does anyone (maybe someone from Firebase or Google) have a warning suppression fix for this at least? – jakedunc Apr 06 '17 at 16:09
  • 32 similar warnings on my side, but also, my app is now broken: network connections start but don't finish and eventually the app completely freezes, probably on some deadlock. It may be unrelated to this issue, but then that's the only compilation problem I have. The same code runs fine when compiled with Xcode 8.2.1 – Guy Moreillon Apr 07 '17 at 06:13
  • A slightly related "protobuf" framework (also from Google) which also caused a lot of warnings seems to have been updated recently - the warnings are gone. Hooray. Now only Firebase warnings remain for me. – Jonny Apr 07 '17 at 06:19
  • Huh, I take back the part about the app being broken in relation to those warnings that I mention above, the app is broken by Xcode 8.3 even with an older version of the Firebase framework that doesn't generate the warnings. – Guy Moreillon Apr 07 '17 at 06:32
  • Same like 39 warnings in my project when after adding firebase to my project through pod. I am just tired of using firebase, it takes too much time to link firebase with google admob, and then same like adding connecting each of admob(banner advertisements and as well as interstitial) again and again and these efforts takes too much time where as time = money, can any one suggest google team to make their process easy for developers instead of time consuming and after spending too much time there is still 39 issues... – Faiz Fareed Apr 10 '17 at 13:38
  • 6
    The fixed pod should be available anytime today. Sorry for the inconvenience. – AniV Apr 11 '17 at 22:27
  • 2
    @AniV Is this going to be an update to the general Firebase pod? So this one: https://cocoapods.org/pods/Firebase. No update yet if so.. – jakedunc Apr 12 '17 at 12:26
  • Ok it's fixed. I hope that notification issue when uploading an app is fixed as well. – cvb Apr 12 '17 at 21:05
  • @ChrisVanBuskirk Nope it is still not fixed – jakedunc Apr 13 '17 at 14:20
  • @jakedunc The notification issue? – cvb Apr 17 '17 at 18:56
  • @ChrisVanBuskirk Yeah I still get an email about "Missing Push Notification Entitlement" when I don't have Push Notifications in my app.. – jakedunc Apr 18 '17 at 10:29
6

This has been fixed in Firebase 3.16.0 (Firebase Core 3.6 + Firebase Analytics 3.8.0)

adbitx
  • 2,019
  • 8
  • 13
  • It's true, a pod update fixed it: `Installing Firebase 3.16.0 (was 3.15.0) Installing FirebaseAnalytics 3.8.0 (was 3.7.0) Installing FirebaseCore 3.6.0 (was 3.5.2)` – aramusss Apr 16 '17 at 16:31
  • @aramusss How Can I update to the new Firebase SDK, is that what I put in my pod – joshLor Apr 21 '17 at 16:25
  • Use pod update in the command line (search on google if any questions) :) – aramusss Apr 21 '17 at 20:24
6

guys, it is all fixed now. Tested it all myself on two projects. You got to go to the correct directory of your project so that your pod spec file is visible to your command line commands, run 

pod update

and see it all fixed and working properly!

Dido
  • 358
  • 3
  • 17
2

These problems are addressed, and likely fixed, with release 3.16.0.

Jonny
  • 15,955
  • 18
  • 111
  • 232