Crash logs

App builds may crash when testing debug builds. Crash logs let you filter these crashed tests and examine crash reports for tests running on BrowserStack devices. BrowserStack detects crashes and produces crash reports, which you can attach to your bug report to help troubleshoot further.

iOS crash log

The iOS crash Logs provide access to the crash reports generated by iOS in the background once a crash occurs. These crash reports include:

• Information about the exception that caused the app to crash.
• A complete backtrace of every thread that ran before the crash.

To diagnose crashes in the app, you can download and share the crash reports with your development team. For more details on how to diagnose issues with crash reports, please refer to the Apple Documentation.

Crash Logs are enabled by default for all Appium iOS sessions and can be accessed from the App Automate dashboard.

Access iOS crash reports from the App Automate dashboard :

Android crash log

The Android crash logs provide detailed reports of crashes generated by Android in the background when a crash occurs. Whenever a build crashes, test runs are marked as crashed and App Automate displays the Crash Logs tab. This tab has details of the exception, process, and stack trace where the crash occurred.

Each crashed session and the build corresponding to it have a crash indicator in BrowserStack. You can also see the count of crashed sessions. If there are multiple crashes, BrowserStack segregates them with a separator.

Access Android crash reports from the App Automate dashboard

To view the Android crash logs, go to the Crash Logs tab from the test sessions details page on the App Automate Dashboard. Click View raw logs to view the crash logs and Download logs to download crash logs.