1. 首頁
  2. 問答
  3. iphone應用程序崩潰：在開發中工作正常，但從iTunes下載時崩潰

iphone應用程序崩潰：在開發中工作正常，但從iTunes下載時崩潰

2011-03-04 88 views
0

我開發了一個應用程序，最近我在蘋果商店中發佈了它。 當我從itunes下載應用程序並啓動它時，它從檢索Web服務中的數據時崩潰。如果我從sdk安裝它，它工作得很好。iphone應用程序崩潰：在開發中工作正常，但從iTunes下載時崩潰

請讓我知道可能是什麼問題？

在此先感謝！

Crash Log 

Code Type:  ARM (Native) 
Parent Process: launchd [1] 

Date/Time:  2011-03-02 18:15:46.353 -0800 
OS Version:  iPhone OS 4.2.1 (8C148) 
Report Version: 104 

Exception Type: EXC_BAD_ACCESS (SIGSEGV) 
Exception Codes: KERN_INVALID_ADDRESS at 0xc9220021 
Crashed Thread: 0 

Thread 0 Crashed: 
0 libobjc.A.dylib     0x33479466 0x33476000 + 13414 
1 CoreFoundation     0x33a5ebb8 0x33a20000 + 256952 
2 Foundation      0x3363978e 0x33619000 + 133006 
3 CoreFoundation     0x33a767d6 0x33a20000 + 354262 
4 CoreFoundation     0x33a485b0 0x33a20000 + 165296 
5 CoreFoundation     0x33a47e54 0x33a20000 + 163412 
6 CoreFoundation     0x33a47c80 0x33a20000 + 162944 
7 CoreFoundation     0x33a47b88 0x33a20000 + 162696 
8 GraphicsServices    0x33b0e4a4 0x33b0a000 + 17572 
9 GraphicsServices    0x33b0e550 0x33b0a000 + 17744 
10 UIKit       0x32099322 0x32062000 + 226082 
11 UIKit       0x32096e8c 0x32062000 + 216716 
12 Bagainfly      0x000020de 0x1000 + 4318 
13 Bagainfly      0x00002074 0x1000 + 4212 

Thread 1: 
0 libSystem.B.dylib    0x33b89974 0x33b5c000 + 186740 
1 libSystem.B.dylib    0x33c33704 0x33b5c000 + 882436 
2 libSystem.B.dylib    0x33c33174 0x33b5c000 + 881012 
3 libSystem.B.dylib    0x33c32b98 0x33b5c000 + 879512 
4 libSystem.B.dylib    0x33bd724a 0x33b5c000 + 504394 
5 libSystem.B.dylib    0x33bcf970 0x33b5c000 + 473456 

Thread 2: 
0 libSystem.B.dylib    0x33b5d268 0x33b5c000 + 4712 
1 libSystem.B.dylib    0x33b5f354 0x33b5c000 + 13140 
2 CoreFoundation     0x33a48648 0x33a20000 + 165448 
3 CoreFoundation     0x33a47ed2 0x33a20000 + 163538 
4 CoreFoundation     0x33a47c80 0x33a20000 + 162944 
5 CoreFoundation     0x33a47b88 0x33a20000 + 162696 
6 WebCore       0x304df124 0x30428000 + 749860 
7 libSystem.B.dylib    0x33bd6886 0x33b5c000 + 501894 
8 libSystem.B.dylib    0x33bcba88 0x33b5c000 + 457352 

Thread 3: 
0 libSystem.B.dylib    0x33b5d268 0x33b5c000 + 4712 
1 libSystem.B.dylib    0x33b5f354 0x33b5c000 + 13140 
2 CoreFoundation     0x33a48648 0x33a20000 + 165448 
3 CoreFoundation     0x33a47ed2 0x33a20000 + 163538 
4 CoreFoundation     0x33a47c80 0x33a20000 + 162944 
5 CoreFoundation     0x33a47b88 0x33a20000 + 162696 
6 Foundation      0x336465f6 0x33619000 + 185846 
7 Foundation      0x33624192 0x33619000 + 45458 
8 Foundation      0x3361d242 0x33619000 + 16962 
9 libSystem.B.dylib    0x33bd6886 0x33b5c000 + 501894 
10 libSystem.B.dylib    0x33bcba88 0x33b5c000 + 457352 

Thread 4: 
0 libSystem.B.dylib    0x33b8168c 0x33b5c000 + 153228 
1 CoreFoundation     0x33a7f662 0x33a20000 + 390754 
2 libSystem.B.dylib    0x33bd6886 0x33b5c000 + 501894 
3 libSystem.B.dylib    0x33bcba88 0x33b5c000 + 457352 

Thread 5: 
0 libSystem.B.dylib    0x33bcba6c 0x33b5c000 + 457324 
1 libSystem.B.dylib    0x33b8a06a 0x33b5c000 + 188522 
2 libsqlite3.dylib    0x3375ca16 0x33748000 + 84502 
3 libsqlite3.dylib    0x3374a88a 0x33748000 + 10378 
4 libsqlite3.dylib    0x33754ffa 0x33748000 + 53242 
5 libsqlite3.dylib    0x33760f40 0x33748000 + 102208 
6 libsqlite3.dylib    0x33774c9c 0x33748000 + 183452 
7 libsqlite3.dylib    0x33788dee 0x33748000 + 265710 
8 libsqlite3.dylib    0x33749de4 0x33748000 + 7652 
9 libsqlite3.dylib    0x33749f6a 0x33748000 + 8042 
10 GMM        0x330ff524 0x330fd000 + 9508 
11 GMM        0x330ff57c 0x330fd000 + 9596 
12 GMM        0x3313743e 0x330fd000 + 238654 
13 MapKit       0x31bf48ca 0x31be4000 + 67786 
14 MapKit       0x31bf480a 0x31be4000 + 67594 
15 CoreFoundation     0x33a767d6 0x33a20000 + 354262 
16 CoreFoundation     0x33a485b0 0x33a20000 + 165296 
17 CoreFoundation     0x33a47e54 0x33a20000 + 163412 
18 CoreFoundation     0x33a47c80 0x33a20000 + 162944 
19 CoreFoundation     0x33a47b88 0x33a20000 + 162696 
20 MapKit       0x31be8906 0x31be4000 + 18694 
21 MapKit       0x31be87ea 0x31be4000 + 18410 
22 libSystem.B.dylib    0x33bd6886 0x33b5c000 + 501894 
23 libSystem.B.dylib    0x33bcba88 0x33b5c000 + 457352 

Thread 6: 
0 libSystem.B.dylib    0x33bd59f0 0x33b5c000 + 498160 
1 libSystem.B.dylib    0x33b8a7ec 0x33b5c000 + 190444 
2 libSystem.B.dylib    0x33b8a3d2 0x33b5c000 + 189394 
3 QuartzCore      0x3412e5dc 0x340f9000 + 218588 
4 QuartzCore      0x340fb01a 0x340f9000 + 8218 
5 libSystem.B.dylib    0x33bd6886 0x33b5c000 + 501894 
6 libSystem.B.dylib    0x33bcba88 0x33b5c000 + 457352 

Thread 7: 
0 libSystem.B.dylib    0x33b5d294 0x33b5c000 + 4756 
1 libSystem.B.dylib    0x33b8b026 0x33b5c000 + 192550 
2 libSystem.B.dylib    0x33b5f258 0x33b5c000 + 12888 
3 libobjc.A.dylib     0x3347a5b8 0x33476000 + 17848 
4 Foundation      0x33630782 0x33619000 + 96130 
5 Foundation      0x336303f4 0x33619000 + 95220 
6 Foundation      0x3363007a 0x33619000 + 94330 
7 MapKit       0x31c10ef0 0x31be4000 + 184048 
8 MapKit       0x31c10e70 0x31be4000 + 183920 
9 GMM        0x33137d66 0x330fd000 + 240998 
10 GMM        0x330fe768 0x330fd000 + 5992 
11 Foundation      0x3364b806 0x33619000 + 206854 
12 Foundation      0x3364b788 0x33619000 + 206728 
13 CFNetwork      0x30ca747e 0x30c98000 + 62590 
14 CFNetwork      0x30c9c1f2 0x30c98000 + 16882 
15 CFNetwork      0x30c9c0e4 0x30c98000 + 16612 
16 CFNetwork      0x30c9c096 0x30c98000 + 16534 
17 CFNetwork      0x30c9c014 0x30c98000 + 16404 
18 CFNetwork      0x30c9bf92 0x30c98000 + 16274 
19 CoreFoundation     0x33a767d6 0x33a20000 + 354262 
20 CoreFoundation     0x33a485b0 0x33a20000 + 165296 
21 CoreFoundation     0x33a47e54 0x33a20000 + 163412 
22 CoreFoundation     0x33a47c80 0x33a20000 + 162944 
23 CoreFoundation     0x33a47b88 0x33a20000 + 162696 
24 MapKit       0x31bf327e 0x31be4000 + 62078 
25 Foundation      0x33624192 0x33619000 + 45458 
26 Foundation      0x3361d242 0x33619000 + 16962 
27 libSystem.B.dylib    0x33bd6886 0x33b5c000 + 501894 
28 libSystem.B.dylib    0x33bcba88 0x33b5c000 + 457352 

Thread 0 crashed with ARM Thread State: 
    r0: 0x001504a0 r1: 0x323738ef  r2: 0x303b83f2  r3: 0x0000004c 
    r4: 0x33a59245 r5: 0xc9220021  r6: 0x3e4f4b74  r7: 0x2fdfec0c 
    r8: 0x303b83f2 r9: 0x2fdfea50  r10: 0x00000000  r11: 0x0013971c 
    ip: 0x3e4efab4 sp: 0x2fdfebec  lr: 0x31c10f53  pc: 0x33479466 
    cpsr: 0x000f0030

來源

2011-03-04 satishdas

+2

您認爲有人會回答您的問題嗎？沒有崩潰日誌，沒有代碼，沒有信息... – Max 2011-03-04 11:17:46

回答

2

當你說在AppleStore中啓動時，你的意思是來自iTunes還是你的意思是它已經被Apple發佈了？

如果你是來自iTunes並且是一個adhoc構建你檢查了你的entitlements.plist？ Another stackoverflow question about entitlements

如果它實際上已獲得批准，並且在AppStore上，您可以查看使用此處的技術生成的崩潰日誌。

How to get crash logs

另一種可能性是，如果你是一個真正的設備連接的第一次，有一個緩慢或間歇性連接和您使用的是同步推出您可能會發現在IOS系統殺死你應用程序，因爲它需要超過10秒的響應時間，所以假設它已經崩潰。

不知道這些是否有助於解決崩潰的更多細節。例如。它在模擬器中是否工作100％，是否可以在Xcode中啓動，它是一個調試/發佈/ adhoc /分發版本，您是否嘗試過使用NSLog消息來縮小它崩潰的位置？

來源

2011-03-04 11:27:14 sradforth

+0

謝謝你的評論...我已經發布了它與分配證書和蘋果批准它，現在它崩潰時有人通過從itunes下載它使用它。 – satishdas 2011-03-04 11:30:01

0

快速地保留了您提交給iTunes的特定版本的dSym文件。

然後，您應該能夠打開在Xcode的系統崩潰日誌，並將它symbolicate像

Bagainfly 0x000020de 0x1000 + 4318 
Bagainfly 0x00002074 0x1000 + 4212

的線條崩潰日誌到您的代碼中有意義的事。希望它會指向你的應用程序崩潰的確切路線。

然而，另一個問題是你只看到冰山一角。 Apple提供給您的崩潰報告經過嚴格過濾。因此，如果您在開發者帳戶中看到了崩潰報告，這意味着您的用戶確實遇到了問題。

我可以推薦一個github項目，讓你的用戶直接發送崩潰報告給你。這樣，當您的用戶開始放棄您的應用程序之前，您會在thigs開始出錯並希望獲得即時通知。 您可以在此處獲取代碼： http://github.com/TheRealKerni/CrashReporterDemo

來源

2011-03-04 12:39:04

相關問題

 相關問題