2015-07-19 37 views
7

語境崩潰中的OpenURL:可能的Facebook SDK的bug的iOS 9

我使用FBSDKLoginButton與我的應用程序。我在Xcode 7.0上,我的iPhone運行的是iOS 9 beta 3.我遵循Facebook顯示的每一步(創建應用程序等),並按照添加按鈕的步驟操作,如https://developers.facebook.com/docs/facebook-login/ios#login-button

正如我在iOS 9,我有一些細微的變化添加到info.plist文件,從而實現跨應用開放:

<key>LSApplicationQueriesSchemes</key> 
<array> 
    <string>fbauth</string> 
</array> 

而且由於從UIAppDelegateopenURL方法改變了iOS9,我改變了openURL代碼段從實這提供:

func application(application: UIApplication, 
    openURL url: NSURL, 
    sourceApplication: String?, 
    annotation: AnyObject?) -> Bool { 
     return FBSDKApplicationDelegate.sharedInstance().application(
      application, 
      openURL: url, 
      sourceApplication: sourceApplication, 
      annotation: annotation) 
} 

這樣:

func application(app: UIApplication, openURL url: NSURL, options: [String : AnyObject]) -> Bool 
{ 
     return FBSDKApplicationDelegate.sharedInstance().application(
      app, 
      openURL: url, 
      sourceApplication: options["UIApplicationOpenURLOptionsSourceApplicationKey"] as? String, 
      annotation: nil) 
} 

問題&問題 所以在這裏我的問題是,即使一切完美(我指的是整個登錄按鈕過程加上來自Facebook的圖形獲取用戶數據)當我運行從模擬器或直接應用在我的iPhone上從XCode,我有一個問題,當我運行我的應用程序相同的過程,但這次從檔案安裝。我曾嘗試使用存檔的IPA文件從OTA應用程序或與Xcode組織者一起安裝的應用程序。在這兩種情況下,當Facebook返回到我的應用程序時,我收到崩潰。由於我無法使用Xcode的調試器,我只有一個崩潰日誌。

Incident Identifier: 842E980C-8DE0-485F-8B3E-8CD889D34B3B 
CrashReporter Key: 3e77866746471e437b9174c6082fc9136a18514f 
Hardware Model:  iPhone7,2 
Process:    Process Name [1086] 
Path:    /private/var/mobile/Containers/Bundle/Application/AA43C098-DFC0-483C-A073-C2401078E9FC/Some App.app/someapp 
Identifier:   fr.someapp.Some-App 
Version:    1 (1.0) 
Code Type:   ARM-64 (Native) 
Parent Process:  launchd [1] 

Date/Time:   2015-07-19 20:18:41.41 +0200 
Launch Time:   2015-07-19 20:18:35.35 +0200 
OS Version:   iOS 9.0 (13A4293g) 
Report Version:  105 

Exception Type: EXC_BREAKPOINT (SIGTRAP) 
Exception Codes: 0x0000000000000001, 0x000000010005f6e4 
Triggered by Thread: 0 

Filtered syslog: 
None found 

Global Trace Buffer (reverse chronological seconds): 
0.228132  AppleJPEG     0x000000018dba5008 [0x13e871e00] Decoding completed without errors 
0.250546  AppleJPEG     0x000000018dba31a0 [0x13e871e00] Options: 1080x1920 [FFFFFFFF,FFFFFFFF] 00025060 
0.250629  AppleJPEG     0x000000018dba3058 [0x13e871e00] Decoding: C0 0x04380780 0x0044304A 0x22111100 0x00000000 175592 
0.256474  AppleJPEG     0x000000018dba5008 [0x13e867200] Decoding completed without errors 
0.261051  AppleJPEG     0x000000018dba31a0 [0x13e867200] Options: 750x1334 [FFFFFFFF,FFFFFFFF] 00025060 
0.261101  AppleJPEG     0x000000018dba3058 [0x13e867200] Decoding: C0 0x02EE0536 0x002F304A 0x22111100 0x00000000 75882 
0.262141  AppleJPEG     0x000000018dba5008 [0x13e85c600] Decoding completed without errors 
0.272075  AppleJPEG     0x000000018dba31a0 [0x13e85c600] Options: 750x1334 [FFFFFFFF,FFFFFFFF] 00025060 
0.272281  AppleJPEG     0x000000018dba3058 [0x13e85c600] Decoding: C0 0x02EE0536 0x002F304A 0x22111100 0x00000000 108826 
0.273070  AppleJPEG     0x000000018dba5008 [0x13f04bc00] Decoding completed without errors 
0.283798  AppleJPEG     0x000000018dba31a0 [0x13f04bc00] Options: 750x1334 [FFFFFFFF,FFFFFFFF] 00025060 
0.283798  AppleJPEG     0x000000018dba3058 [0x13f04bc00] Decoding: C0 0x02EE0536 0x002F304A 0x22111100 0x00000000 72967 
5.783070  CFNetwork     0x0000000186041d44 TCP Conn 0x13e5a1b90 SSL Handshake DONE 
5.874750  CFNetwork     0x0000000186041c54 TCP Conn 0x13e5a1b90 starting SSL negotiation 
5.875481  CFNetwork     0x00000001860e0e14 TCP Conn 0x13e5a1b90 complete. fd: 6, err: 0 
5.876954  CFNetwork     0x00000001860e21e4 TCP Conn 0x13e5a1b90 event 1. err: 0 
5.984181  CFNetwork     0x00000001860e22f8 TCP Conn 0x13e5a1b90 started 
5.992333  CFNetwork     0x0000000186137140 Creating default cookie storage with default identifier 
5.992333  CFNetwork     0x000000018613710c Faulting in CFHTTPCookieStorage singleton 
5.992562  CFNetwork     0x0000000186188068 Faulting in NSHTTPCookieStorage singleton 
6.189612  AppleJPEG     0x000000018dba234c [0x13e871e00] Created session 
6.190797  AppleJPEG     0x000000018dba234c [0x13e867200] Created session 
6.192109  AppleJPEG     0x000000018dba234c [0x13e85c600] Created session 
6.197484  AppleJPEG     0x000000018dba234c [0x13f04bc00] Created session 



Thread 0 name: Dispatch queue: com.apple.main-thread 
Thread 0 Crashed: 
0 Some app      0x000000010005f6e4 function signature specialization <Arg[0] = Owned To Guaranteed, Arg[1] = Owned To Guaranteed, Arg[2] = Owned To Guaranteed and Exploded, Arg[3] = Dead> of Some_App.AppDelegate.application (Some_App.AppDelegate)(ObjectiveC.UIApplication, openURL : ObjectiveC.NSURL, options : [Swift.String : Swift.AnyObject]) -> Swift.Bool (AppDelegate.swift:100) 
1 Some_app      0x000000010005e7a8 @objc Some_App.AppDelegate.application (Some_app.AppDelegate)(ObjectiveC.UIApplication, openURL : ObjectiveC.NSURL, options : [Swift.String : Swift.AnyObject]) -> Swift.Bool (AppDelegate.swift:0) 
2 UIKit       0x000000018c1ee664 0x18bf34000 + 2860644 
3 UIKit       0x000000018c1ee168 0x18bf34000 + 2859368 
4 UIKit       0x000000018c1f5c30 0x18bf34000 + 2890800 
5 UIKit       0x000000018c1fb644 0x18bf34000 + 2913860 
6 UIKit       0x000000018c1fa9dc 0x18bf34000 + 2910684 
7 UIKit       0x000000018c1e6fd4 0x18bf34000 + 2830292 
8 UIKit       0x000000018c1e6eb4 0x18bf34000 + 2830004 
9 FrontBoardServices    0x00000001905ffbe0 0x1905d8000 + 162784 
10 FrontBoardServices    0x00000001905fff60 0x1905d8000 + 163680 
11 CoreFoundation     0x00000001868eb8b4 0x18680c000 + 915636 
12 CoreFoundation     0x00000001868eb348 0x18680c000 + 914248 
13 CoreFoundation     0x00000001868e901c 0x18680c000 + 905244 
14 CoreFoundation     0x00000001868157fc 0x18680c000 + 38908 
15 GraphicsServices    0x00000001918a316c 0x191898000 + 45420 
16 UIKit       0x000000018bfae5e4 0x18bf34000 + 501220 
17 Some app      0x000000010005eaa4 main (AppDelegate.swift:14) 
18 libdyld.dylib     0x000000019bb128b4 0x19bb10000 + 10420 

看來,當Facebook的回調我的應用程序在我AppDelegateopenURL方法發生崩潰。如上所述,從iOS9開始,有兩種方法可以對這種方法進行編碼,並且我嘗試了這兩種方法。如果我刪除方法內的Facebook代碼,那麼我不會崩潰,但我不登錄。所以崩潰的線是Facebook的路線。它只會崩潰,如果我的應用程序從檔案安裝。有任何想法嗎?可能Facebook的SDK在這個特定情況下有一個錯誤?

回答

11

我發現我的答案

看起來就像是一個釋放模式唯一的問題。通過啓用Xcode來運行Release版本,我可以調試我的問題。它是由參數sourceApplication引起的,在發佈模式下顯然需要爲unwrapped。不知道爲什麼,但至少我讓它工作。

func application(app: UIApplication, openURL url: NSURL, options: [String : AnyObject]) -> Bool 
{ 
     return FBSDKApplicationDelegate.sharedInstance().application(
      app, 
      openURL: url, 
      sourceApplication: options["UIApplicationOpenURLOptionsSourceApplicationKey"] as! String, 
      annotation: nil) 
} 
+0

謝謝。這是拯救我的一天。 –

+0

@Valentin Mercier,我使用的是客觀的C,我也面臨類似的問題。如果我從我的機器運行構建,它不會崩潰,但是當我從同事構建運行相同的構建時,它會崩潰。所以你可以就此提出建議。 – Ranjit