title: Facebook SDK v4 & Parse (Swift)
body: <p>I am trying to work ParseFacebookUtilsv4 &amp; FacebookSDK v4.. After many trials, I've managed to reduce the errors to 1.</p>
  
  <pre><code>func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -&gt; Bool {
  
      Parse.setApplicationId("###",
          clientKey: "###")
  
      PFFacebookUtils.initializeFacebookWithLaunchOptions(launchOptions)
  
  }
  </code></pre>
  
  <p>In this part, which is exactly copied from <a href="https://parse.com/docs/ios_guide#fbusers-setup/iOS" rel="nofollow">Parse's iOS Docs - Facebook Setup</a> (that is updated yesterday for FBSDKv4), I am getting an error:</p>
  
  <pre><code>'PFFacebookUtils.Type' does not have a member named 'initializeFacebookWithLaunchOptions'
  </code></pre>
  
  <p>When I check the full documentation of <a href="https://www.parse.com/docs/ios/api/Classes/PFFacebookUtils.html" rel="nofollow">ParseFacebookUtilsv4</a> which says ~ <em>Warning: This class supports official Facebook iOS SDK v4.0+ and is available only on iOS.</em> ~, I saw that there isn't any class called <strong>'initializeFacebookWithLaunchOptions'</strong>; instead there is <strong>'initializeFacebookWithApplicationLaunchOptions:'</strong></p>
  
  <p>However, when I change my AppDelegate.swift / didFinishLaunchingWithOptions part as:</p>
  
  <pre><code>func application(application: UIApplication, didFinishLaunchingWithOptions launchOptions: [NSObject: AnyObject]?) -&gt; Bool {
  
      Parse.setApplicationId("###",
          clientKey: "###")
  
      PFFacebookUtils.initializeFacebookWithApplicationLaunchOptions(launchOptions)
  
  }
  </code></pre>
  
  <p>...I get an error saying 'Missing return in a function expected to return 'Bool'. Then I tried to add both</p>
  
  <pre><code> return true /* AND */ return false // at the end of the function; 
  </code></pre>
  
  <p>...I get 9 crashes such as:
  i.stack.imgur.com/o989R.png</p>
  
  <p>I am completely stuck and don't know how to fix this.</p>