-
Notifications
You must be signed in to change notification settings - Fork 0
/
23353173.zh-CN.001.xlf
585 lines (585 loc) · 61.7 KB
/
23353173.zh-CN.001.xlf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
<file source-language="en" target-language="zh-CN" datatype="htmlbody" original="https://stackoverflow.com/questions/23353173">
<body>
<group id="23353173">
<trans-unit id="a215145f3d3cea020467b0a82ee5677c1446ea97" translate="yes" xml:space="preserve">
<source>. Make sure your emulator or device is selected in the <code>Devices</code> panel. Next, try to find the stack trace, which is shown in red. There may be a lot of stuff logged into logcat, so you may need to scroll a bit. An easy way to find the stack trace is to clear the logcat (using the recycle bin on the right), and let the app crash again.</source>
<target state="translated">。 确保在&ldquo; <code>Devices</code> 面板中选择了仿真器或设备。 接下来，尝试找到以红色显示的堆栈跟踪。 可能有很多东西登录到logcat中，因此您可能需要滚动一下。 查找堆栈跟踪的一种简单方法是清除logcat（使用右侧的回收站），然后让应用再次崩溃。</target>
</trans-unit>
<trans-unit id="253405e7811c600857109e7c1cf106fbb6ee4d33" translate="yes" xml:space="preserve">
<source><a href="https://developer.android.com/studio/command-line/logcat.html">HERE</a> is the Android's page about logcat</source>
<target state="translated"><a href="https://developer.android.com/studio/command-line/logcat.html">这里</a>是关于logcat的Android页面</target>
</trans-unit>
<trans-unit id="5dcfeeee1724d0d53219254dfe0ac82132e1c799" translate="yes" xml:space="preserve">
<source><em>About this question - obviously inspired by <a href="https://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors">What is a stack trace, and how can I use it to debug my application errors?</a>, there are lots of questions stating that their application has crashed, without any further detail. This question aims to instruct novice Android programmers on how to try and fix their problems themselves, or ask the right questions.</em></source>
<target state="translated"><em>关于这个问题-显然是受<a href="https://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors">什么是堆栈跟踪的</a>启发，以及如何使用它来调试应用程序错误？</em> <em>，有很多问题表明它们的应用已崩溃，没有任何进一步的细节。</em> <em>这个问题旨在指导新手Android程序员如何自行解决问题或提出正确的问题。</em></target>
</trans-unit>
<trans-unit id="a1742e3f2bffc6e6b7a0ec0aaf5550830f76efeb" translate="yes" xml:space="preserve">
<source><em>This answer describes the process of retrieving the stack trace. Already have the stack trace? Read up on stack traces in "<a href="https://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors">What is a stack trace, and how can I use it to debug my application errors?</a>"</em></source>
<target state="translated"><em>此答案描述了检索堆栈跟踪的过程。</em> <em>已经有堆栈跟踪了吗？</em> <em>在&ldquo; <a href="https://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors">什么是堆栈跟踪，以及如何使用它来调试应用程序错误？</a> &rdquo;中阅读堆栈跟踪。</em></target>
</trans-unit>
<trans-unit id="a0cb9036b6ad3c88783ffc9da95ea7d26428669a" translate="yes" xml:space="preserve">
<source><em>adb logcat &gt; logcat.txt</em></source>
<target state="translated"><em>亚行logcat&gt; logcat.txt</em></target>
</trans-unit>
<trans-unit id="5675776236029f09b45cdd52142ec4b52f209174" translate="yes" xml:space="preserve">
<source><strong><code>gradlew build &gt; log.txt 2&gt;details.txt</code></strong></source>
<target state="translated"><strong> <code>gradlew build &gt; log.txt 2&gt;details.txt</code> </strong></target>
</trans-unit>
<trans-unit id="80501ebd4a00b1d4443479dc2dcea7e4a4110d51" translate="yes" xml:space="preserve">
<source><strong><em>Note 2:</em></strong><em>I am considering that your device is successfully connected.</em></source>
<target state="translated"><strong><em>注意2：</em></strong> <em>我正在考虑您的设备已成功连接。</em></target>
</trans-unit>
<trans-unit id="7ef8a5a042a622521e98dbe5a04d1b185d68a91f" translate="yes" xml:space="preserve">
<source><strong><em>Note:</em></strong><em> This answer is using Android Studio 2.2.2</em></source>
<target state="translated"><strong><em>注意：</em></strong> <em>此答案使用的是Android Studio 2.2.2</em></target>
</trans-unit>
<trans-unit id="50d0c2d486e8899a547895532d7a03f049fd80af" translate="yes" xml:space="preserve">
<source><strong>Analyzing</strong></source>
<target state="translated"><strong>Analyzing</strong></target>
</trans-unit>
<trans-unit id="ddaa01a990fa55c62dde6f67f0c8959b7499d799" translate="yes" xml:space="preserve">
<source><strong>Capturing</strong></source>
<target state="translated"><strong>Capturing</strong></target>
</trans-unit>
<trans-unit id="175dd94f5456ec4928585d1666d4ec711c42cf37" translate="yes" xml:space="preserve">
<source><strong>Click on that blue link</strong>. It should take you to where the problem occured. In my case, it was due to this line:</source>
<target state="translated"><strong>单击该蓝色链接</strong> 。 它应该带您到发生问题的位置。 就我而言，这是由于以下原因：</target>
</trans-unit>
<trans-unit id="fdb78ad9807f38f53d55df3d9d555e5c753c29cf" translate="yes" xml:space="preserve">
<source><strong>Common error during app crash like:</strong></source>
<target state="translated"><strong>应用程序崩溃期间的常见错误，例如：</strong></target>
</trans-unit>
<trans-unit id="c2f473bf4cebda35c92dc33ddd44a1e5d12e2e66" translate="yes" xml:space="preserve">
<source><strong>DOCS</strong></source>
<target state="translated"><strong>DOCS</strong></target>
</trans-unit>
<trans-unit id="35e122cab5bc5a5f2296f0fcf79278ece15df1f5" translate="yes" xml:space="preserve">
<source><strong>How to do that?</strong></source>
<target state="translated"><strong>怎么做？</strong></target>
</trans-unit>
<trans-unit id="80f0fb9807597a2a6d5eeca2f9c9b84f2c975e11" translate="yes" xml:space="preserve">
<source><strong>If that <code>Caused by:</code></strong> DOESN'T have a line with a blue text somewhere under it, then look for another <code>Caused by:</code> that does.</source>
<target state="translated"><strong>如果是 <code>Caused by:</code> 原因引起的：</strong>在其下的某处没有一行带有蓝色文本的行，然后查找另一 <code>Caused by:</code> 原因引起的：那样。</target>
</trans-unit>
<trans-unit id="d15b2fd36fa70e7af4be5d2633fec743eb796326" translate="yes" xml:space="preserve">
<source><strong>Logcat</strong> - <strong>To check the logs in the development phase of Android Studio</strong></source>
<target state="translated"><strong>Logcat-</strong> <strong>在Android Studio的开发阶段检查日志</strong></target>
</trans-unit>
<trans-unit id="015ccc4ce17285116ceb1e59b99b11b21c3f6eca" translate="yes" xml:space="preserve">
<source><strong>Next to</strong> that <code>Caused By:</code>, there should be the Exception that happened. In my case, it's a <code>RuntimeException</code> and <strong>under it</strong> there should be a line which contains a <strong>blue link</strong> such as:</source>
<target state="translated"><strong>在</strong> <code>Caused By:</code> <strong>旁边</strong> ，应该有发生的异常。 就我而言，这是一个 <code>RuntimeException</code> ， <strong>在它的</strong>下面应该有一行，其中包含一个<strong>蓝色链接，</strong>例如：</target>
</trans-unit>
<trans-unit id="1d7ddb9ca9305db3b69febe087986d85bdca4704" translate="yes" xml:space="preserve">
<source><strong>Overview</strong></source>
<target state="translated"><strong>Overview</strong></target>
</trans-unit>
<trans-unit id="db45c105e26924c54e27641e8f8e759270f7425f" translate="yes" xml:space="preserve">
<source><strong>To resolve app crash error:</strong></source>
<target state="translated"><strong>解决应用崩溃错误：</strong></target>
</trans-unit>
<trans-unit id="4c566898bec7b59122fa1b57e63ad626b0e8e296" translate="yes" xml:space="preserve">
<source>A NULL Pointer Exception error</source>
<target state="translated">A NULL 指针异常错误</target>
</trans-unit>
<trans-unit id="d2c34de080511b786d7d5cc7f2ccd65d6d17a517" translate="yes" xml:space="preserve">
<source>Activity missing in AndroidManifest file.</source>
<target state="translated">AndroidManifest文件中缺少活动。</target>
</trans-unit>
<trans-unit id="0a64722b73dbf88db687567ec6e39a20f5f0f6ff" translate="yes" xml:space="preserve">
<source>After that, you find which point your app has stopped fix that from your point.</source>
<target state="translated">在这之后,你发现你的应用程序已经停止了从你的点修复的哪一点。</target>
</trans-unit>
<trans-unit id="033dd6410056e382480733e4ef72f3848ccf1002" translate="yes" xml:space="preserve">
<source>After that, you find which point your app has stopped it's very easy to solve at your side.</source>
<target state="translated">之后,你发现你的APP停止了哪一点,在你的身边很容易解决。</target>
</trans-unit>
<trans-unit id="05801dd87ebf1885e87ebb998cbd5445d51c55a2" translate="yes" xml:space="preserve">
<source>Also running this command in terminal can help find the problem:</source>
<target state="translated">同时在终端中运行此命令可以帮助查找问题。</target>
</trans-unit>
<trans-unit id="c950be9a99edef9700e290a8eb552cc5fc12a273" translate="yes" xml:space="preserve">
<source>Android Debug Monitor or Android Device Monitor(type command <strong>monitor</strong> or open through UI)</source>
<target state="translated">Android调试监视器或Android设备监视器（键入命令<strong>监视器</strong>或通过UI打开）</target>
</trans-unit>
<trans-unit id="a0461b370c97320db4eadce615521905410d30a0" translate="yes" xml:space="preserve">
<source>Android Studio</source>
<target state="translated">安卓工作室</target>
</trans-unit>
<trans-unit id="2e35d99abb3b79dd9a2eb3da6d7070300aa09a56" translate="yes" xml:space="preserve">
<source>Basic tool from Android to collect/analyse logs is the logcat.</source>
<target state="translated">来自安卓系统的基本工具,收集分析日志的基本工具是logcat。</target>
</trans-unit>
<trans-unit id="de29669dd9cfa902f42faca0d5a0961f1c9fbe5d" translate="yes" xml:space="preserve">
<source>Basically I forgot to do this in my onCreate():</source>
<target state="translated">基本上我忘了在我的onCreate()中这样做了。</target>
</trans-unit>
<trans-unit id="63b61f586e48fd9e0db9cdb67616937af064af5e" translate="yes" xml:space="preserve">
<source>Basically, you can MANUALLY capture logcat with following command (or just check AndroidMonitor window in AndroidStudio):</source>
<target state="translated">基本上,你可以通过以下命令手动捕获logcat(或者在AndroidStudio中检查AndroidMonitor窗口)。</target>
</trans-unit>
<trans-unit id="0a3951ba0343eafdecabf813150232d982b128b2" translate="yes" xml:space="preserve">
<source>Best way to check is through <em>Logcat</em> if you are still developing the app in Android studio which is quick way to read stack trace and check the cause of the app.</source>
<target state="translated">如果您仍在Android Studio中开发应用程序，则最好的检查方法是通过<em>Logcat</em> ，这是读取堆栈跟踪并检查应用程序原因的快速方法。</target>
</trans-unit>
<trans-unit id="33bdf7f2c2b74786885833f2f8002a91c9705fd4" translate="yes" xml:space="preserve">
<source>Change "<code>Verbose</code>" to "<code>Error</code>" Now it will only show you logged errors. Don't worry about all these errors (if you got them) now.</source>
<target state="translated">将&ldquo; <code>Verbose</code> &rdquo;更改为&ldquo; <code>Error</code> &rdquo;，现在它将仅显示记录的错误。 现在就不必担心所有这些错误（如果有）。</target>
</trans-unit>
<trans-unit id="45228be6b8846c174952bfd7d920ab01c99fd218" translate="yes" xml:space="preserve">
<source>Check your <code>Logcat</code> message and see your <code>Manifest</code> file. There should be something missing like defining the <code>Activity,</code>User permission`, etc.</source>
<target state="translated">检查您的 <code>Logcat</code> 消息并查看 <code>Manifest</code> 文件。 应该缺少一些东西，例如定义&ldquo; <code>Activity,</code> 用户权限&rdquo;等。</target>
</trans-unit>
<trans-unit id="93cc6804d673c5d025f5b9cf57b4ad8adf474b9d" translate="yes" xml:space="preserve">
<source>Click on the "Android Monitor" (The one I underlined in the image above. ^)</source>
<target state="translated">点击 "安卓监控器"(我在上图中下划线的那个)。</target>
</trans-unit>
<trans-unit id="38cee37d9824a785ce5a8c4f64ed33c38dd93e89" translate="yes" xml:space="preserve">
<source>Coding mistake(Wrong use of keywords).</source>
<target state="translated">编码错误(关键词使用错误)。</target>
</trans-unit>
<trans-unit id="044a7653226b9518e3cd49b368ae1fff859eccb2" translate="yes" xml:space="preserve">
<source>Crash during development</source>
<target state="translated">发展过程中的碰撞</target>
</trans-unit>
<trans-unit id="8b83133fa73b47680cf9c4f7367aa03ff15f5b9b" translate="yes" xml:space="preserve">
<source>Crash in the wild</source>
<target state="translated">在野外撞车</target>
</trans-unit>
<trans-unit id="95caa7282da1a153114b9b5b1c59768332368e55" translate="yes" xml:space="preserve">
<source>Declared but not defined.</source>
<target state="translated">已宣布,但未确定。</target>
</trans-unit>
<trans-unit id="11c60a30e428f5e98d32fbee63cced814e4b3dfb" translate="yes" xml:space="preserve">
<source>Detailed info about the error: <code>Attempt to invoke virtual method 'void android.support.v4.app.FragmentActivity.onBackPressed()' on a null object reference</code></source>
<target state="translated">有关该错误的详细信息： <code>Attempt to invoke virtual method 'void android.support.v4.app.FragmentActivity.onBackPressed()' on a null object reference</code></target>
</trans-unit>
<trans-unit id="caf9d89374f1969a1cfac09a984f329e13a721f6" translate="yes" xml:space="preserve">
<source>Error happened in file <code>com.example.khan.abc.AudioFragment.java</code>, inside <code>onClick()</code> method at line: <code>125</code> (stacktrace shows the line that error happened)</source>
<target state="translated">错误 <code>com.example.khan.abc.AudioFragment.java</code> 文件中的 <code>onClick()</code> 方法中的错误发生在第 <code>125</code> 行（stacktrace显示发生错误的行）</target>
</trans-unit>
<trans-unit id="4d997704aaa124982e14877fd5a273cfca5b98f2" translate="yes" xml:space="preserve">
<source>Every time an Android application crashes (or any Java application for that matter), a <code>Stack trace</code> is written to the console (in this case, logcat). This stack trace contains vital information for solving your problem.</source>
<target state="translated">每当Android应用程序崩溃（或与此相关的任何Java应用程序）崩溃时，都会将 <code>Stack trace</code> 写入控制台（在本例中为logcat）。 此堆栈跟踪包含解决问题的重要信息。</target>
</trans-unit>
<trans-unit id="1561666572b07a4184586a98a6c181774556a83c" translate="yes" xml:space="preserve">
<source>First, you check which point your app has crashed (<code>Unfortunately, MyApp has stopped.</code>). For this, you can use <code>Log.e("TAG", "Message");</code>, using this line you can see your app log in logcat.</source>
<target state="translated">首先，您检查您的应用崩溃了的那一点（ <code>Unfortunately, MyApp has stopped.</code> ）。 为此，可以使用 <code>Log.e("TAG", "Message");</code> ，使用此行，您可以在logcat中看到您的应用程序日志。</target>
</trans-unit>
<trans-unit id="d806bc4aaca17be39fb201279369fc2f1cda5624" translate="yes" xml:space="preserve">
<source>First, you need to check where and why your app has been crashed <code>(Unfortunately, MyApp has stopped.).</code> With the help of <code>LOG</code>, you can figure it out what went wrong.</source>
<target state="translated">首先，您需要检查应用程序崩溃的位置和原因 <code>(Unfortunately, MyApp has stopped.).</code> 借助 <code>LOG</code> ，您可以找出问题所在。</target>
</trans-unit>
<trans-unit id="b45ea78797c7a2395f7b5591b28a105681377df2" translate="yes" xml:space="preserve">
<source>For more information, check on <a href="https://source.android.com/devices/tech/debug">https://source.android.com/devices/tech/debug</a>.</source>
<target state="translated">有关更多信息，请检查<a href="https://source.android.com/devices/tech/debug">https://source.android.com/devices/tech/debug</a> 。</target>
</trans-unit>
<trans-unit id="2dbfd5bee894dd4b40888a05b7b4cb6cfe66c2d8" translate="yes" xml:space="preserve">
<source>Go to the LogCat, from the drop down menu select error. This will contain all the required information to help you debug. If that doesn't help, post the LogCat as an edit to your question and somebody will help you out.</source>
<target state="translated">转到LogCat,从下拉菜单中选择错误。这将包含所有需要的信息来帮助你调试。如果没有帮助,请将LogCat作为你的问题的编辑发布,会有人帮你解决。</target>
</trans-unit>
<trans-unit id="fa6020b54bac56e946ea081da56066a1737a69a5" translate="yes" xml:space="preserve">
<source>How to solve it?</source>
<target state="translated">如何解决?</target>
</trans-unit>
<trans-unit id="54025b82ef4418aadce9bed1bc66f252f8d49047" translate="yes" xml:space="preserve">
<source>However, let's say I got another error:</source>
<target state="translated">然而,让我们说我又出错了。</target>
</trans-unit>
<trans-unit id="d315fb149fab1cd8395ba990b2ced89675e82f21" translate="yes" xml:space="preserve">
<source>I am developing an application, and everytime I run it, I get the message:</source>
<target state="translated">我正在开发一个应用程序,每次运行时都会收到这样的信息。</target>
</trans-unit>
<trans-unit id="19f3a14eb4d6449b8fef33daffe68a058b53efd6" translate="yes" xml:space="preserve">
<source>I checked my logcat, I clicked on the blue link it gave me, and it took me here:</source>
<target state="translated">我检查了我的日志猫,我点击了它给我的蓝色链接,它把我带到了这里。</target>
</trans-unit>
<trans-unit id="88a512987f3bc842d45d9f2d739ad69312c7bb29" translate="yes" xml:space="preserve">
<source>I have <code>private TextView mTextView</code> declared at the top of my class. But, I'm not defining it.</source>
<target state="translated">我在班级顶部声明了 <code>private TextView mTextView</code> 。 但是，我没有定义它。</target>
</trans-unit>
<trans-unit id="91443d71fe058c7246c6bf63820d676e4f4c412f" translate="yes" xml:space="preserve">
<source>I have found the stack trace, now what?</source>
<target state="translated">我找到了栈道的痕迹,现在呢?</target>
</trans-unit>
<trans-unit id="67ce8f0ed4e09b928cc3b10c6e963773b3132ef7" translate="yes" xml:space="preserve">
<source>I hope I could help you someway...
Regards</source>
<target state="translated">希望我能帮到你......尊敬的各位.....</target>
</trans-unit>
<trans-unit id="4196ada75f212bc56aced85dafb9c30fbcfcb254" translate="yes" xml:space="preserve">
<source>I observe my code, now I notice something.</source>
<target state="translated">我观察我的代码,现在我注意到了一些事情。</target>
</trans-unit>
<trans-unit id="439b0d0551eb68bf35709af4017d645a2f68dcd4" translate="yes" xml:space="preserve">
<source>I still can't solve my problem!</source>
<target state="translated">我还是没能解决我的问题!</target>
</trans-unit>
<trans-unit id="ca3424c26a8bc2408c0dcd2205c505f86087274a" translate="yes" xml:space="preserve">
<source>I suggest to use <strong>Android Debug Monitor</strong>, it is good. Because eclipse hangs when too many logs are there, and through adb logcat filter and all difficult.</source>
<target state="translated">我建议使用<strong>Android Debug Monitor</strong> ，这很好。 因为当日志太多时，eclipse会挂起，并且通过adb logcat过滤器会很困难。</target>
</trans-unit>
<trans-unit id="8b193b65da52d2111c6ec880a8b61b9aa975b644" translate="yes" xml:space="preserve">
<source>If adding Permission, declare it in the <code>AndroidMainifest</code> file as well.</source>
<target state="translated">如果添加了权限，则还要在 <code>AndroidMainifest</code> 文件中声明它。</target>
</trans-unit>
<trans-unit id="8ecf0d0715d15784a4a750d07547cd6063466a3c" translate="yes" xml:space="preserve">
<source>If you app is Crashing, you'll get something like:</source>
<target state="translated">如果你的应用程序崩溃了,你会得到类似的东西。</target>
</trans-unit>
<trans-unit id="ddbf8dc90b5f70bafca4dc254288e6a08f33b9f1" translate="yes" xml:space="preserve">
<source>If you cant see the logcat windows go to this path and open it</source>
<target state="translated">如果你看不到logcat窗口,请到这个路径打开它</target>
</trans-unit>
<trans-unit id="9f3205a125184717e7251dee4fcdd4587a7645a0" translate="yes" xml:space="preserve">
<source>If you don't have any kind of interesting log in your terminal (or they are not directly related to your app), maybe your problem is due to a native library. In that case, you should check for the "tombstone" files within your terminal.</source>
<target state="translated">如果你的终端中没有任何有趣的日志(或者它们与你的应用程序没有直接关系),也许你的问题是由于原生库造成的。在这种情况下,你应该检查你的终端中的 "墓碑 "文件。</target>
</trans-unit>
<trans-unit id="e5c7dea4856e9ee58202dc5c7804e1dc39696ad0" translate="yes" xml:space="preserve">
<source>If you don't like it, there're a lot of alternative <a href="https://stackoverflow.com/q/4325073/1429387">desktop log viewers for Android</a>.</source>
<target state="translated">如果您不喜欢它，则有许多其他<a href="https://stackoverflow.com/q/4325073/1429387">的Android桌面日志查看器</a> 。</target>
</trans-unit>
<trans-unit id="8c7f2d2fa75fdb56c72c2b65d929f90f2ab7d1d9" translate="yes" xml:space="preserve">
<source>If you use android Studio, you can also check this <a href="https://developer.android.com/studio/debug/index.html#systemLogView">LINK</a>.</source>
<target state="translated">如果您使用的是android Studio，还可以检查此<a href="https://developer.android.com/studio/debug/index.html#systemLogView">LINK</a> 。</target>
</trans-unit>
<trans-unit id="b83eb69188ab563f640bf55a54250e2f0a69d1a7" translate="yes" xml:space="preserve">
<source>If you've found your <code>Exception</code> and the line where it occurred, and still cannot figure out how to fix it, don't hesitate to ask a question on StackOverflow.</source>
<target state="translated">如果您已经找到了 <code>Exception</code> 及其发生的行，但是仍然想不出解决方法，请随时在StackOverflow上提问。</target>
</trans-unit>
<trans-unit id="73d1a15151172771c84bd87d9e0bff2d278c5613" translate="yes" xml:space="preserve">
<source>If your app for some reason crashes without good stacktrace. Try debug it from first line, and go line by line until crash. Then you will have answer, which line is causing you trouble. Proably you could then wrapp it into try catch block and print error output.</source>
<target state="translated">如果你的应用程序由于某种原因而崩溃,没有很好的栈跟踪。试着从第一行开始调试,逐行进行调试,直到崩溃。然后你就会知道是哪一行造成了你的麻烦。也许你可以把它包装成try catch块,然后打印错误输出。</target>
</trans-unit>
<trans-unit id="eb6cd095ff6fbe37fdc1761a2c0845620e8c742f" translate="yes" xml:space="preserve">
<source>If your app is already live, then you can not use <em>logcat</em>. So, for that you can implement <code>Crashlytics</code> to provide you bug reports of any exception that occurs.</source>
<target state="translated">如果您的应用程序已经上线，则不能使用<em>logcat</em> 。 因此，为此，您可以实施 <code>Crashlytics</code> ,以向您提供发生的任何异常的错误报告。</target>
</trans-unit>
<trans-unit id="822f3d226a2c48f50362271306967b577b3a9f66" translate="yes" xml:space="preserve">
<source>In below showToast() method you have to pass another parameter for context or application context by doing so you can try it.</source>
<target state="translated">在下面的showToast()方法中,你必须传递另一个参数作为上下文或应用程序上下文的参数,这样你就可以尝试一下。</target>
</trans-unit>
<trans-unit id="4f4fcb7ff8e9cc0290756b411e57cf41f9eb2edf" translate="yes" xml:space="preserve">
<source>In the bottom bar of the window, click on the <code>Logcat</code> button. Alternatively, you can press</source>
<target state="translated">在窗口的底部栏中，单击 <code>Logcat</code> 按钮。 或者，您可以按</target>
</trans-unit>
<trans-unit id="c5ad89ddb14036e82a89584ef0b9b5e9a32aba78" translate="yes" xml:space="preserve">
<source>In this case you need to make sure your Android manifest is configured correctly (including any manifest merging happening from a library and any activity that would come from a library), and pay particular attention to the first activity displayed in your application in your manifest files.</source>
<target state="translated">在这种情况下,你需要确保你的Android manifest的配置是正确的(包括任何从库中发生的 manifest 合并和任何来自库中的活动),并特别注意你的应用程序中显示的第一个活动在你的 manifest 文件中。</target>
</trans-unit>
<trans-unit id="872a2df18969fb0fbec5afe84dc17ccf2ce04494" translate="yes" xml:space="preserve">
<source>Initially clear the Logcat and let the app crash again so you can get only crashed log detail. You have to check the Stack trace</source>
<target state="translated">最初清除Logcat并让应用程序再次崩溃,这样你就只能得到崩溃的日志细节。你必须检查Stack trace</target>
</trans-unit>
<trans-unit id="d6c89e96e11c2e812189ce3b40908c12b8211a35" translate="yes" xml:space="preserve">
<source>Integrate a real-time crash reporting tool such as <a href="https://firebase.google.com/docs/crashlytics">Firebase Crashlytics</a> in order to get stacktraces of unhandled exceptions which occurred on users' devices.</source>
<target state="translated">集成了诸如<a href="https://firebase.google.com/docs/crashlytics">Firebase Crashlytics之</a>类的实时崩溃报告工具，以获取用户设备上发生的未处理异常的堆栈跟踪 。</target>
</trans-unit>
<trans-unit id="f65b2cfd144efb285465e97d6056b7db23a42718" translate="yes" xml:space="preserve">
<source>It is important to check when the issue happened... You may find several errors in a log... you must be sure that you are checking the proper messages :)</source>
<target state="translated">检查问题发生的时间很重要......你可能会在日志中发现几个错误...........你必须确保你检查的信息是正确的 :)</target>
</trans-unit>
<trans-unit id="102f4c79ac080dbbdd0c46706ccfe1f7c1801328" translate="yes" xml:space="preserve">
<source>It was called by:</source>
<target state="translated">它被称为。</target>
</trans-unit>
<trans-unit id="50d7b95b1a368987d7d6a246469a1e31376d0211" translate="yes" xml:space="preserve">
<source>Just check the error in log cat.</source>
<target state="translated">只要检查一下日志猫中的错误就可以了。</target>
</trans-unit>
<trans-unit id="06cd7721c3679c8af0f607497f8d84d7562eea14" translate="yes" xml:space="preserve">
<source>Keep in mind above points and go through it.</source>
<target state="translated">牢牢记住以上几点,然后再过一遍。</target>
</trans-unit>
<trans-unit id="103dea4d1ae126480ab02f19de815e878441eb24" translate="yes" xml:space="preserve">
<source>Let me share a basic Logcat analysis for when you meet a Force Close (when app stops working).</source>
<target state="translated">下面我给大家分享一个基本的Logcat分析,当你遇到强制关闭(当APP停止工作的时候)。</target>
</trans-unit>
<trans-unit id="5a90905e7d506db8c8dd193986908778600f2339" translate="yes" xml:space="preserve">
<source>Log cat contains error.</source>
<target state="translated">Log cat包含错误。</target>
</trans-unit>
<trans-unit id="cdd1e0238b1beac2f605f13766cc3eb5d68935a3" translate="yes" xml:space="preserve">
<source>Make sure if u create a new <code>activity</code>, always declare the <code>activity</code> in the <code>AndroidManifest</code> file.</source>
<target state="translated">确保是否创建新 <code>activity</code> ，请始终在 <code>AndroidManifest</code> 文件中声明该 <code>activity</code> 。</target>
</trans-unit>
<trans-unit id="ef588cf3934d257fb79c9f7060db8a795def6ea5" translate="yes" xml:space="preserve">
<source>Make sure to mark <code>./logview</code> and <code>./lib/logview.jar</code> as executable when running in Linux.</source>
<target state="translated">在Linux中运行时，请确保将 <code>./logview</code> 和 <code>./lib/logview.jar</code> 标记为可执行文件。</target>
</trans-unit>
<trans-unit id="d7e347b3fc3e8ee61edf8e660158c57e0941f74b" translate="yes" xml:space="preserve">
<source>Mismatch property name.</source>
<target state="translated">错配属性名称。</target>
</trans-unit>
<trans-unit id="b90a2391f56c58af038c1b469e593390b469fe6e" translate="yes" xml:space="preserve">
<source>Mismatch version(maybe).</source>
<target state="translated">错配版(也许)。</target>
</trans-unit>
<trans-unit id="3644d9a2ee229e6bbcc875c3d78e185824f51d61" translate="yes" xml:space="preserve">
<source>Most common NullPointerException.</source>
<target state="translated">最常见的NullPointerException。</target>
</trans-unit>
<trans-unit id="ea780c93044cc8c687a569943794cb7f73d9cdfb" translate="yes" xml:space="preserve">
<source>Notice <code>Log.d</code> has a first parameter,in our case "AppDebug". Click on the "No Filters" drop down menu on the top-right of the logcat. Select "Edit Filter Configuration", give a name to your filter, and in "Log Tag" put "App Debug". Click "OK". Now, you should see two lines in the logcat:</source>
<target state="translated">注意 <code>Log.d</code> 具有第一个参数，在我们的示例中为&ldquo; AppDebug&rdquo;。 单击logcat右上方的&ldquo;无过滤器&rdquo;下拉菜单。 选择&ldquo;编辑过滤器配置&rdquo;，为过滤器命名，然后在&ldquo;日志标签&rdquo;中输入&ldquo;应用程序调试&rdquo;。 点击&ldquo;确定&rdquo;。 现在，您应该在logcat中看到两行：</target>
</trans-unit>
<trans-unit id="590fbdd857cc0f84e8f0c1231e1e45912ebd6d14" translate="yes" xml:space="preserve">
<source>Now, like we did previously (We changed Verose to Error), we want to change "Error" to "Debug". Since we're logging by debugging. Here's all the Log methods:</source>
<target state="translated">现在,就像我们之前做的那样(我们把Verose改成了Error),我们要把 "Error "改成 "Debug"。既然我们要通过调试来记录。下面是所有的日志方法。</target>
</trans-unit>
<trans-unit id="d19c75bbbb75a534ae9890bdb427fbc0187ad3dd" translate="yes" xml:space="preserve">
<source>Now, you'll get something like this:</source>
<target state="translated">现在,你会得到这样的东西。</target>
</trans-unit>
<trans-unit id="51f8b5e6dc0d5993aeb44478487d19e6bf3e18c9" translate="yes" xml:space="preserve">
<source>Ok. Now, do what you did to crash your app. After your app crashes, go to your logcat. You should find a new crash log that has a lot of <code>at:x.x.x</code>: and <code>Caused by: TrumpIsPresidentException</code> for example. Go to that <code>Caused by:</code> statement in your logcat.</source>
<target state="translated">好。 现在，执行崩溃应用程序的操作。 应用崩溃后，转到日志目录。 例如，您应该找到一个新的崩溃日志，其中有很多 <code>at:x.x.x</code> ：，并且 <code>Caused by: TrumpIsPresidentException</code> 。 转到您的logcat中的 <code>Caused by:</code> 语句。</target>
</trans-unit>
<trans-unit id="e09e16def7e85a8d6efa4f345125b42f782285a3" translate="yes" xml:space="preserve">
<source>Other wise you can also check the error by executing an application in debug mode.
Firstly set breakpoint after that by doing:</source>
<target state="translated">另外,你也可以通过在调试模式下执行应用程序来检查错误。首先设置断点,然后再做。</target>
</trans-unit>
<trans-unit id="508ddd59ad73bfef48c7b0f00d997b8c7f961a75" translate="yes" xml:space="preserve">
<source>People make mistakes, and so coding as well.</source>
<target state="translated">人都会犯错,所以编码也是如此。</target>
</trans-unit>
<trans-unit id="293fa3251837c6b14672288ffacc9e3e38848dd4" translate="yes" xml:space="preserve">
<source>Permission missing in AndroidManifest file.</source>
<target state="translated">AndroidManifest文件中缺少权限。</target>
</trans-unit>
<trans-unit id="b548bb0f5438c7440b5c7b442ffa77801ddd4744" translate="yes" xml:space="preserve">
<source>Read <a href="https://tech.trello.com/how-to-release-a-buggy-app-and-live-to-tell-the-story/">How to Release a Buggy App (And Live to Tell the Tale)</a> to know more about handling bugs in the field.</source>
<target state="translated">阅读<a href="https://tech.trello.com/how-to-release-a-buggy-app-and-live-to-tell-the-story/">如何发布Buggy应用程序（并现场讲述故事），</a>以了解有关在现场处理错误的更多信息。</target>
</trans-unit>
<trans-unit id="60666776c3e37a6b3a50de04704ebc6e4b36fb3d" translate="yes" xml:space="preserve">
<source>Read up on stack traces in "<a href="https://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors">What is a stack trace, and how can I use it to debug my application errors?</a>"</source>
<target state="translated">在&ldquo; <a href="https://stackoverflow.com/questions/3988788/what-is-a-stack-trace-and-how-can-i-use-it-to-debug-my-application-errors">什么是堆栈跟踪，以及如何使用它来调试应用程序错误？</a> &rdquo;中阅读堆栈跟踪。</target>
</trans-unit>
<trans-unit id="5f42023d6505b1032cc7e6a28242ba92c8c188d6" translate="yes" xml:space="preserve">
<source>So THAT'S why <code>mTextView</code> is null, because I forgot to tell my app what it is. So I add that line, run my app, and now the app doesn't crash.</source>
<target state="translated">所以这就是为什么 <code>mTextView</code> 为null的原因，因为我忘了告诉我的应用程序了。 因此，我添加了这一行，运行我的应用程序，现在该应用程序不会崩溃。</target>
</trans-unit>
<trans-unit id="7838a138696b66514576fec2cb0e9824871e509f" translate="yes" xml:space="preserve">
<source>So now we know that mTextView is null.</source>
<target state="translated">所以现在我们知道mTextView是空的。</target>
</trans-unit>
<trans-unit id="a7defb600d35cb420d8517c6afc6f5f9faedd9d8" translate="yes" xml:space="preserve">
<source>So, let's find out <strong>what is null</strong>. There's two possibilities. Either <code>mTextView</code> is null, or <code>myString</code> is null. To find out, before the <code>mTextView.setText(mString)</code> line, I add these two lines:</source>
<target state="translated">因此，让我们找出<strong>什么是null</strong> 。 有两种可能性。 <code>mTextView</code> 为null或 <code>myString</code> 为null。 为了找出 <code>mTextView.setText(mString)</code> ，在mTextView.setText（mString）行之前，添加了这两行：</target>
</trans-unit>
<trans-unit id="96053eefb7bbc2e3b9823e45ee0dbccd3ffe4879" translate="yes" xml:space="preserve">
<source>So, now I know why it's crashing. It's because I'm throwing the exception myself. <strong>This was an obvious error</strong>.</source>
<target state="translated">所以，现在我知道为什么它崩溃了。 这是因为我自己抛出了异常。 <strong>这是一个明显的错误</strong> 。</target>
</trans-unit>
<trans-unit id="c1450c6f60c12ccd09e5e3d2d12a582ade5e3ef6" translate="yes" xml:space="preserve">
<source>So, now I want to debug. According to <a href="https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it">this StackOverflow question</a>, a NullPointerException says that something is <code>null</code>.</source>
<target state="translated">所以，现在我要调试。 根据<a href="https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it">这个StackOverflow问题</a> ，NullPointerException表示某些内容为 <code>null</code> 。</target>
</trans-unit>
<trans-unit id="bedf23ff950028539b173605cce23051ed984351" translate="yes" xml:space="preserve">
<source>So, since we used <code>Log.d</code>, we're checking in Debug. That's why we changed it to debug.</source>
<target state="translated">因此，由于我们使用了 <code>Log.d</code> ，因此我们正在检查Debug。 这就是为什么我们将其更改为调试。</target>
</trans-unit>
<trans-unit id="3d1ed854eb0c6a189b7566d07fae0395bb8a0191" translate="yes" xml:space="preserve">
<source>Stack Trace: Stack Trace shows you the method invocation order... Sometimes, the error happens in the calling method (and not in the called method).</source>
<target state="translated">堆栈跟踪。堆栈跟踪显示方法调用顺序......有时,错误发生在调用方法中(而不是在被调用的方法中)。</target>
</trans-unit>
<trans-unit id="355c15d3884285cbe9de6e8c0623457a61fdc6ca" translate="yes" xml:space="preserve">
<source>The Problem</source>
<target state="translated">问题所在</target>
</trans-unit>
<trans-unit id="fd683620086136da881a4c83473c21e4d3b35361" translate="yes" xml:space="preserve">
<source>The default location for the tombstone files depends on every device, but if that's the case, you will have a log telling: <code>Tombstone written to: /data/tombstones/tombstone_06</code></source>
<target state="translated">逻辑删除文件的默认位置取决于每个设备，但如果是这样，您将有一条日志告诉： <code>Tombstone written to: /data/tombstones/tombstone_06</code></target>
</trans-unit>
<trans-unit id="7f32dcb8de851ea6f95e03a73d26e7f0027e396f" translate="yes" xml:space="preserve">
<source>The first thing you do when your application crashes is look into the LogCat, at the bottom of Android Studio there's a toolbar with a list of menus:</source>
<target state="translated">当你的应用程序崩溃时,你要做的第一件事就是查看LogCat,在Android Studio的底部有一个工具栏,上面有一个菜单列表。</target>
</trans-unit>
<trans-unit id="0788073483e4940f0c92a536ec07804a2933b649" translate="yes" xml:space="preserve">
<source>The most common of these is the <a href="https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it"><code>NullPointerException</code></a>.</source>
<target state="translated">其中最常见的是<a href="https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it"> <code>NullPointerException</code> </a> 。</target>
</trans-unit>
<trans-unit id="80622c7f8d30a36ec271e72c774f95d032248c26" translate="yes" xml:space="preserve">
<source>There's a lot of parameters you can add to command which helps you to filter and display the message that you want... This is personal... I always use the command below to get the message timestamp:</source>
<target state="translated">有很多参数可以添加到命令中,帮助你过滤和显示你想要的信息。这是我个人的看法.....我总是用下面这个命令来获取消息的时间戳。</target>
</trans-unit>
<trans-unit id="e1bfd2fc08a018e53bc3ef828d4974c6af2f0acc" translate="yes" xml:space="preserve">
<source>This part of the log shows you a lot of information:</source>
<target state="translated">这一部分的日志给你展示了很多信息。</target>
</trans-unit>
<trans-unit id="79df7925e83cdd14cac004893edc6c721c7a6183" translate="yes" xml:space="preserve">
<source>This popup shows only when you get a fatal exception in your code which stops the execution of the app. It could be any exception <code>NullPointerException</code>, <code>OutOfMemoryException</code> etc.</source>
<target state="translated">仅当您的代码中出现致命异常并停止执行应用程序时，才会显示此弹出窗口。 它可以是 <code>NullPointerException</code> ， <code>OutOfMemoryException</code> 等任何异常。</target>
</trans-unit>
<trans-unit id="32fe0adc1e4541fa0d50573cad901adc56aabf93" translate="yes" xml:space="preserve">
<source>This was just an overview... Not all logs are simple etc... It is just to share the idea and provide a entry-level information to you...</source>
<target state="translated">这只是一个概述.....不是所有的日志都很简单等等.....。只是想和大家分享一下,给大家提供一个入门级的资料......</target>
</trans-unit>
<trans-unit id="a20a38e0c7e83a5c85e6c762bc2bc5be37e4aa00" translate="yes" xml:space="preserve">
<source>This way, you know which app crashed (to be sure that you are checking the logs about your message)</source>
<target state="translated">这样一来,你就知道是哪个应用程序崩溃了(为了确定你正在检查关于你的信息的日志</target>
</trans-unit>
<trans-unit id="9b2fc463509d09fe5c9f61df50e79e71015a3baa" translate="yes" xml:space="preserve">
<source>To see Logcat if you use <strong>Android Studio</strong> then Press <strong>ALT + 6</strong>
or</source>
<target state="translated">要查看Logcat（如果您使用的是<strong>Android Studio），请</strong>按<strong>ALT + 6</strong>或</target>
</trans-unit>
<trans-unit id="77f62db26434dba5e8faf629b11ac8c2cf5e83b2" translate="yes" xml:space="preserve">
<source>Try my favourite tool <a href="https://bitbucket.org/mlopatkin/android-log-viewer/downloads/">logview</a> to get the logs and analyze them during development.</source>
<target state="translated">尝试使用我最喜欢的工具<a href="https://bitbucket.org/mlopatkin/android-log-viewer/downloads/">logview</a>获取日志并在开发过程中对其进行分析。</target>
</trans-unit>
<trans-unit id="8b5e8ea29bdb3cc571d163dd9986eae9369b15d3" translate="yes" xml:space="preserve">
<source>Try to be as concise as possible: post the stack trace, and the <em>relevant</em> code (e.g. a few lines up to the line which threw the <code>Exception</code>).</source>
<target state="translated">尽量简明扼要：发布堆栈跟踪和<em>相关</em>代码（例如，在抛出 <code>Exception</code> 的行之前增加几行）。</target>
</trans-unit>
<trans-unit id="358e8259260e0be41dd584e9c570ec1fa3963595" translate="yes" xml:space="preserve">
<source>Unfortunately MyApp has stopped. How can I solve this</source>
<target state="translated">不幸的是,MyApp停止了。我该如何解决这个问题?</target>
</trans-unit>
<trans-unit id="d45e85197d8d56de09c79faaceaf609a66c73c71" translate="yes" xml:space="preserve">
<source>Unfortunately, MyApp has stopped.</source>
<target state="translated">遗憾的是,MyApp已经停止了。</target>
</trans-unit>
<trans-unit id="d63d3c31b541121eeefaa8fd2d6fa3300ae5c9f6" translate="yes" xml:space="preserve">
<source>Unsupported plugin(maybe).</source>
<target state="translated">不支持的插件(也许)。</target>
</trans-unit>
<trans-unit id="5e37789cca1c6accbcf4730a8a2b43359cc39d28" translate="yes" xml:space="preserve">
<source>Use the <strong>LogCat</strong> and try to find what is causing the app to crash.</source>
<target state="translated">使用<strong>LogCat</strong>并尝试查找导致应用程序崩溃的原因。</target>
</trans-unit>
<trans-unit id="7ecf79a6a50db25f2363cb7b39de210815ca5c52" translate="yes" xml:space="preserve">
<source>What can I do to solve this?</source>
<target state="translated">有什么办法可以解决这个问题?</target>
</trans-unit>
<trans-unit id="730bc33321574afd36ea5d6b24a5220cc2c0de46" translate="yes" xml:space="preserve">
<source>When ever any <code>error</code> happened, always check with the logcat with the text in red color however u can find out the <em>real problem in blue color text with underline</em> in those red color text.</source>
<target state="translated">如果发生任何 <code>error</code> ，请始终检查带有红色文本的logcat，但是您可以找出红色<em>文本中带有下划线的蓝色文本</em>的<em>实际问题</em> 。</target>
</trans-unit>
<trans-unit id="38e13f8e8cf7955dbb18d5cd8dad4d445df9ffb3" translate="yes" xml:space="preserve">
<source>When the issue happened: <code>07-09 08:29:13.475</code></source>
<target state="translated">问题发生的时间： <code>07-09 08:29:13.475</code></target>
</trans-unit>
<trans-unit id="63374e29cef2a86fc3204747d940693fb8d94cff" translate="yes" xml:space="preserve">
<source>Which ERROR: <code>java.lang.NullPointerException</code></source>
<target state="translated">哪个错误： <code>java.lang.NullPointerException</code></target>
</trans-unit>
<trans-unit id="daa96ef6aa257e22d3f231c991140b1decc77ebd" translate="yes" xml:space="preserve">
<source>Which app crashed: <code>com.example.khan.abc</code></source>
<target state="translated">哪个应用崩溃了： <code>com.example.khan.abc</code></target>
</trans-unit>
<trans-unit id="21412830c60fef4feb00085e0c43498e0c599f37" translate="yes" xml:space="preserve">
<source>Which was called by:</source>
<target state="translated">这是由。</target>
</trans-unit>
<trans-unit id="754c6220126e2ae6fb6815367759ac7e33ac3d05" translate="yes" xml:space="preserve">
<source>While, Unfortunately, MyApp has stopped. There are many reasons for it. You can check same in logs. For this, you can use the Log.e("TAG","Message");</source>
<target state="translated">虽然,不幸的是,MyApp已经停止了。有很多原因。你可以在日志中检查同样的原因。为此,你可以使用Log.e("TAG","Message")。</target>
</trans-unit>
<trans-unit id="f3e5956d0a8b9eb2a6b2af2e84fdab84e4a5ff75" translate="yes" xml:space="preserve">
<source>With the error, you will get the file name also in blue colour (click on them and jump to code from error is occurring).</source>
<target state="translated">在错误的情况下,你会得到蓝色的文件名(点击它们并跳转到错误发生的代码)。</target>
</trans-unit>
<trans-unit id="8ffc495839d6c605c379d3e2536b81f9a3fe9adc" translate="yes" xml:space="preserve">
<source>Yay! You're halfway to solving your problem.</source>
<target state="translated">好啊!你的问题已经解决了一半了。</target>
</trans-unit>
<trans-unit id="8c7256f8b6ec7a4a0c3583a8ef39b5779ab79921" translate="yes" xml:space="preserve">
<source>You can also get this error message on its own, without any stack trace or any further error message.</source>
<target state="translated">你也可以单独得到这个错误信息,没有任何堆栈跟踪,也没有任何进一步的错误信息。</target>
</trans-unit>
<trans-unit id="5c4f1fbe371e86c7e60d41a644f8fa9ca0209e7a" translate="yes" xml:space="preserve">
<source>You can redirect the output to a file and analyze it in a Text Editor.</source>
<target state="translated">你可以将输出重定向到一个文件,在文本编辑器中进行分析。</target>
</trans-unit>
<trans-unit id="2bbaeafa73b769ebeeb4e48bfbed2f8b07135ec0" translate="yes" xml:space="preserve">
<source>You can use <a href="https://developer.android.com/studio/command-line/adb.html">Google's ADB tool</a> to get <code>Logcat file</code> to analyze the issue.</source>
<target state="translated">您可以使用<a href="https://developer.android.com/studio/command-line/adb.html">Google的ADB工具</a>获取 <code>Logcat file</code> 来分析问题。</target>
</trans-unit>
<trans-unit id="808687efe8119b3dd0df760db07c0f1214005789" translate="yes" xml:space="preserve">
<source>You can use any of these tools:</source>
<target state="translated">你可以使用这些工具中的任何一个。</target>
</trans-unit>
<trans-unit id="58d79c27153ba64668e6631c06f5326ae336e525" translate="yes" xml:space="preserve">
<source>You get the log cat option from in eclipse:</source>
<target state="translated">你可以从eclipse中获得日志猫选项。</target>
</trans-unit>
<trans-unit id="51f7668bf058d16687ae548cdac338b29f5c14c2" translate="yes" xml:space="preserve">
<source>You have to check the <code>Stack trace</code></source>
<target state="translated">您必须检查 <code>Stack trace</code></target>
</trans-unit>
<trans-unit id="942d746ede39abc185f1cb553adc9bde9d8d0e7e" translate="yes" xml:space="preserve">
<source>You only need to find out what exactly made your application crash, by analyzing the stack trace.</source>
<target state="translated">你只需要通过分析堆栈跟踪,找出到底是什么让你的应用崩溃。</target>
</trans-unit>
<trans-unit id="b46437cb509dca24b70d4342f75a99a3ae41e008" translate="yes" xml:space="preserve">
<source>You tried to call method <code>onBackPressed()</code> from a <code>FragmentActivity</code> object. However, that object was <code>null</code> when you did it.</source>
<target state="translated">您试图从 <code>FragmentActivity</code> 对象调用方法 <code>onBackPressed()</code> 。 但是，该对象在您执行操作时为 <code>null</code> 。</target>
</trans-unit>
<trans-unit id="301243d9f882c32abe82947fd97e9e261424e784" translate="yes" xml:space="preserve">
<source>Your application quit because an uncaught <code>RuntimeException</code> was thrown.</source>
<target state="translated">您的应用程序退出，因为引发了未捕获的 <code>RuntimeException</code> 。</target>
</trans-unit>
<trans-unit id="ae0a6d876e07c940c8c6a773ab9a3af5889acaaa" translate="yes" xml:space="preserve">
<source>adb logcat</source>
<target state="translated">adb logcat</target>
</trans-unit>
<trans-unit id="29c80bbab5b1d70a1b50ce24d80be82fb94af6ab" translate="yes" xml:space="preserve">
<source>adb logcat &gt; logs.txt (you can use editors to open and search errors.)</source>
<target state="translated">adb logcat&gt; logs.txt（您可以使用编辑器打开和搜索错误。）</target>
</trans-unit>
<trans-unit id="325562c769da3f80d0e63bb56514bc2e2723c9b5" translate="yes" xml:space="preserve">
<source>alt</source>
<target state="translated">alt</target>
</trans-unit>
<trans-unit id="2be35c13df79ebc096b072e312fcd5735912c6f0" translate="yes" xml:space="preserve">
<source>at com.example.khan.abc.AudioFragment$1.onClick(AudioFragment.java:125)</source>
<target state="translated">at com.example.han.abc.AudioFragment$1.onClick(AudioFragment.java:125)</target>
</trans-unit>
<trans-unit id="3c188fcb768144032d8f47d179581d181095c8b8" translate="yes" xml:space="preserve">
<source>eclipse logcat (If not visible in eclipse, Go to Windows-&gt;Show View-&gt;Others-&gt;Android-&gt;LogCat)</source>
<target state="translated">eclipse logcat（如果在eclipse中不可见，请转到Windows-&gt;显示视图-&gt;其他-&gt; Android-&gt; LogCat）</target>
</trans-unit>
<trans-unit id="e8d7f36a6be00bd41ceb44237294a90b66899f40" translate="yes" xml:space="preserve">
<source>etc....</source>
<target state="translated">etc....</target>
</trans-unit>
<trans-unit id="1c92a7dc8f2ecf8f17067c681dc8a388c4d93ff4" translate="yes" xml:space="preserve">
<source>if you are using Google-Api go to this path</source>
<target state="translated">如果你使用的是Google-API,请转到这个路径</target>
</trans-unit>
<trans-unit id="1ff187142dffb2a9d2fba35bc1de0dcb32cd9083" translate="yes" xml:space="preserve">
<source>if you use <strong>Eclipse</strong> then
<strong>Window -&gt; Open Perspective -&gt; Other - LogCat</strong></source>
<target state="translated">如果使用<strong>Eclipse，</strong>则<strong>窗口-&gt;打开透视图-&gt;其他-LogCat</strong></target>
</trans-unit>
<trans-unit id="7c5dbe21bfa7d2b49d5bab64c142ea8053307306" translate="yes" xml:space="preserve">
<source>on Your IDE Check the windows form LOGCAT</source>
<target state="translated">在您的集成开发环境中检查窗口中的LOGCAT表格</target>
</trans-unit>
<trans-unit id="f6de1d309b43f69118c378e05edeb7cafe02ca80" translate="yes" xml:space="preserve">
<source>open <code>logcat.txt</code> file and search for your application name. There should be information on why it failed, the line number, Class name, etc.</source>
<target state="translated">打开 <code>logcat.txt</code> 文件并搜索您的应用程序名称。 应该有关于失败原因，行号，类名等的信息。</target>
</trans-unit>
<trans-unit id="98b156eea2c8e8eac12be56072d82f362c6dcbff" translate="yes" xml:space="preserve">
<source>right click on project-&gt;debug as-&gt;Android application</source>
<target state="translated">右键单击项目-&gt;调试为-&gt; Android应用程序</target>
</trans-unit>
<trans-unit id="bc3cd611361993934f5cbe26b39e40729e521cb6" translate="yes" xml:space="preserve">
<source>then you should go to gradlew file location in read two above log files.</source>
<target state="translated">那么你应该去读取上面两个日志文件中的gradlew文件位置。</target>
</trans-unit>
<trans-unit id="685449ca44465887f7eb9a9a7b5231a91c8e5260" translate="yes" xml:space="preserve">
<source>which was called by:</source>
<target state="translated">它被称为:</target>
</trans-unit>
<trans-unit id="b42a08daacc13ebac0acb4532b5c80eab0089f65" translate="yes" xml:space="preserve">
<source>window-&gt;show view-&gt;others-&gt;Android-&gt;Logcat</source>
<target state="translated">窗口-&gt;显示视图-&gt;其他-&gt; Android-&gt; Logcat</target>
</trans-unit>
</group>
</body>
</file>
</xliff>