5

I have updated my Podspec to include the latest Facebook SDK 3.9 (of writing) and I am now seeing a bunch of warnings.

Should I be looking to resolve these: enter image description here

A few of these should be simple solutions like updating nil to be 0 instead as expected.

What is the best practice, just to leave these for a minor fix release which should resolve them?

For reference and searching:

Incompatible pointer to integer conversion sending 'void *' to parameter of type 'NSRegularExperssionOptions' (aka 'enum NSregularExperssionOptions')
Unused function 'FBReadIntBigEndian'

Bibhas Debnath
  • 14,559
  • 17
  • 68
  • 96
StuartM
  • 6,743
  • 18
  • 84
  • 160

2 Answers2

9

Changing the files locally would not be very helpful, because someday the files will be overwritten.

You can let Facebook know about these issues and while they don't solve it you can ignore the warnings by changing you Podfile to something like this:

platform :ios

# ignore all warnings from all pods
inhibit_all_warnings!

# ignore warnings from a specific pod
pod 'Facebook-iOS-SDK', :inhibit_warnings => true

(Podfile copied from this answer).

Community
  • 1
  • 1
Marcelo
  • 9,916
  • 3
  • 43
  • 52
2

I filed a bug - https://developers.facebook.com/bugs/724535024243347 - to which the Facebook guys replied that it's in my code and it's not their fault. After which I've submitted a pull request that fixes/suppresses the warnings in their code - https://github.com/facebook/facebook-ios-sdk/pull/563 Hopefully they'll integrate that one.

Andrew
  • 3,166
  • 21
  • 32
  • Thanks @Andrew - I had the same issue, so fixed locally and changed the pod not to update, but I see they still exist in later versions. Good work with the pull request and good luck with them accepting it ;) – StuartM Dec 02 '13 at 16:17