You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-4Lines changed: 8 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,8 +72,8 @@ catch (e: Exception) {
72
72
73
73
# Supported SDKs <aname="supported-sdks"></a>
74
74
* Minimum SDK version 21 (Android 5.0)
75
-
* Target SDK version 28 (Android 9.0)
76
-
* Minimum NDK version 17c
75
+
* Target SDK version 30 (Android 11.0)
76
+
* Minimum NDK version 16b
77
77
* Maximum NDK version 22
78
78
79
79
# Supported platforms
@@ -516,6 +516,10 @@ In addition, you may need to add the [extractNativeLibs](https://developer.andro
516
516
```
517
517
More details about [extractNativeLibs](https://developer.android.com/guide/topics/manifest/application-element#extractNativeLibs) are available from the Android documentation
518
518
519
+
**NOTE:** If your native app is built with NDK 16b, the Breakpad native crash client will be used instead of our recommended Crashpad crash client. To avoid this please use NDK 17c+ to build your native app.
520
+
521
+
**NOTE:** Breakpad crash reports are submitted on the next app startup, instead of at crash time like Crashpad crash reports
522
+
519
523
## Uploading symbols to Backtrace
520
524
For an NDK application, debugging symbols are not available to Backtrace by default. You will need to upload the application symbols for your native code to Backtrace. You can do this by uploading the native libraries themselves, which are usually found in the .apk bundle. [Click here to learn more about symbolification](https://support.backtrace.io/hc/en-us/articles/360040517071-Symbolication-Overview)
521
525
@@ -527,12 +531,12 @@ To enable client side unwinding, you can call the `setupNativeIntegration` metho
**NOTE:** Client side unwinding is only available in API level 23+ (Android 6.0)+
531
-
532
534
**NOTE:** When viewing a crash in the Backtrace Debugger, it may still show warning messages that symbols are missing from certain frames after client-side unwinding is performed. This warning is expected if these symbols are not available on the Backtrace server, and should have no impact to the end-user's ability to read the call stack.
533
535
534
536
**NOTE:** Client side unwinding is only available for fatal crashes. Non-fatal Crashpad dumps you generate via `DumpWithoutCrash` for instance will not use client side unwinding.
535
537
538
+
**NOTE:** Client side unwinding is only available in NDK level 17+ (i.e: Only with the Crashpad crash reporting backend)
539
+
536
540
### Unwinding Modes and Options
537
541
538
542
You can optionally specify the unwinding mode (`REMOTE_DUMPWITHOUTCRASH` is the default)
set_property(TARGET base PROPERTY IMPORTED_LOCATION${PROJECT_SOURCE_DIR}/crashpad-builds/${ANDROID_ABI}/third_party/mini_chromium/mini_chromium/base/libbase.a)
set_property(TARGET base PROPERTY IMPORTED_LOCATION${PROJECT_SOURCE_DIR}/crashpad-builds/${ANDROID_ABI}/third_party/mini_chromium/mini_chromium/base/libbase.a)
0 commit comments