How to use Device Logs in Android and iOS to report issues

Nobody likes it when their mobile applications crash abruptly when while using it. According to research bydotcominfowayapproximately 62 % of the audience uninstall the app if they see clank.

To help with the diagnosing of the problem, the operation system of our device generates a ‘ device log ’. This guide helps you realise how to use device log to account issue in a wandering covering.

What are Device Logs?

Device logs are system-generated logs that are used to supervise the operation of a device. The gimmick logs consist of the log messages and stock of twist command and applied policy. It also control all the detailed information on the operations that take place in the operating system and the applications. It can help you analyse the application logs in a device.

These are particularly helpful when an application in the device is be tested and the application crashes. The device logs are wide used to report issues in Android and iOS covering.

What does Device Logs contain?

Device logs contain elaborate records of a twist & # 8217; s activities, operation, and events that occur during its use. These logs are valuable for trouble-shoot, debugging, and monitoring the execution of device, especially in wandering and web app testing.

These logs assist developers and testers identify issues, translate behaviour patterns, and improve the overall constancy and performance of devices and applications.

Generally, device logs include:

1. System Events: Information about device startup, shutdown, and system-level changes or updates.
2. App Activity: Logs related to the launching, backgrounding, or termination of applications, including any errors or crashes.
3. Network Requests: Details about network interactions, including HTTP requests, reaction, errors, and the status of connections.
4. Error Messages: Specific error messages or heap ghost touch to package issues, clangoring, or bugs.
5. User Interactions: Logs related to user activity, such as button click, touch events, or navigation within an app.
6. Hardware Interactions: Data associate to hardware components, like battery status, GPS, sensors, or twist depot.
7. Security Events: Information on security case, including assay-mark, encoding, and potential vulnerabilities or breaches.
8. Performance Metrics: Data related to CPU usage, retention intake, app responsiveness, and overall execution during app execution.

Using Device Logs to Report Issues in an Android App

When an application crashes or there is a trouble with running an coating, you can use device logs to report these issues on an Android gimmick. If you are wondering how to get logarithm from an Android device, say the upcoming subdivision.

1. Using Android Device Logs on BrowserStack

BrowserStack offers two products to test your mobile applications on a range of Android devices. The products are:

App Live

is an effective production that developers and QA can use to test mobile applications. You can review the product use its costless trial option. To use App Live to test your mobile applications,

1. .
2. Select the twist that you want to examine on
3. Then you will see a developer & # 8217; s screen on the rightfield and an Android earphone templet on the unexpended side of the screen. You can use the respective functionality on the blind like Record Session, DevTools, etc
4. Now, to get the device log for a particular application, prize Dev Tools and All Device Logs.

App Automate

assist its user to test native and hybrid applications on real Android devices. You can desegregate various screen model like,, EarlGrey,, etc with App Automate. You can use BrowserStack & # 8217; s App Automate to debug your applications instantly using text logs, screenshots of test footrace, picture transcription, etc.

App Automate helps developers to transport lineament updates at a faster rate by reducing the build clip by more than 10 times the normal pace via. App Automate complies with Service Organisation Control (SOC) 2, hence you breathe insure that all your builds are perfectly secure. They change their privacy policy regularly since user security is one of their prime schedule.

SUSA automates exploratory testing with persona-driven behavior, catching bugs that scripted automation misses.

2. Bug Report Feature from your Android Device

A bug report consists of heap traces, device logs, and diagnostic info to aid you in locating and fixing the bug in your application. To beguile a bug study, from your Android earpiece:

1. Enable Developer option on your gimmick
2. From the Developer options, select Take bug report.
3. Then choose the kind of bug study you want to create and selectReport.
4. You will incur a telling when the select bug report is ready.
5. If you want to parcel the bug story with external collaborators, select the notification and share it.

3. Create Android Bug Reports with the Android Debug Bridge (ADB)

You can likewise create bug story using the Android Debug Bridge (ADB).

If you hold a single connected gimmick, the following bid creates a bug account.

$ adb bugreport E: \Reports\MyBugReports

In the above command, if you do not ply a specific path for the study, it will be saved to the local directory.

If you hold multiple affiliated device, you need to delimitate the device where you want to save the story with the -s selection.

Use the below bid to get the serial figure of the twist and so create the bug report.

$ adb device

List of device attached

emulator-5554 device 8XR7N16C31003476 twist

$ adb -s 8XR7N16C31003476 bugreport

Using Device Logs to Report Issues in an iOS App

Devices using iOS maintain continuous gimmick logs of all the operations occurring in the iOS and the case-by-case applications. These device logs can be accessed after an topic hap. Let & # 8217; s say you have topic instal an covering, you can diagnose the issue by reviewing the device log via the Console app on macOS.

1. Using iOS Device Logs on BrowserStack

You can use the effective products offered by BrowserStack (App Live and App Automate) to view the gimmick logs of your Apple device. BrowserStack offer superior features and they are one of the best in the market.

Talk to an Expert

App Live

is an effective product that developer and QA can use to prove peregrine coating. You can review the merchandise using its free trial alternative. To use App Live to quiz your mobile application,

1. .
2. Select the gimmick that you require to try on
3. Then you will see a developer & # 8217; s screen on the rightfield and an Android earpiece template on the unexpended side of the screen. You can use the various functionality on the screen like Record Session, DevTools, etc
4. Now, to get the device log for a particular application, blue-ribbon Dev Tools and All Device Logs.

App Automate

helps its exploiter to essay native and hybrid application on existent Android device. You can integrate various testing frameworks like Appium, Espresso, EarlGrey, XCUITest, etc with App Automate. You can also use this program to debug your coating instantly using text log, screenshots of exam runs, video recordings, etc.

2. Using your physical iPhone or iPad

You can too view the gimmick logs using your iPhone or iPad. To access the twist logs using your iPhone or iPad, you demand to postdate these steps:

1. Tap on Settings on the home screen and select Privacy
2. Scroll downwards and select the Analytics alternative
3. Then click on Analytics information to view the inclination of twist log related to app crashes
4. You can further tick on one of the clang and view the elaborated log of events.

Unlike BrowserStack products, this list is not very user-friendly. However, it can be useful in sure situations such as the occasional crash of a particular application.

3. Using iTools

iTools is mainly used to access the device logs of an iOS device when you have a Windows figurer sooner than an Apple Mac Computer. Follow the measure below to accession the gimmick logs of an iOS gimmick via an application call iTools:

1. Download iTools. You can select iTools for Windows or Mac depending on the operating system of your twist
2. Install the iTools covering and launching it
3. Plug in the iOS device to your computer and unlock your iOS gimmick
4. As soon as your iOS device connects to the reckoner, you will see a prompt asking you to trust the device
5. Select Trust on the device
6. You can receive a free trial of iTools
7. Click on Toolbox and so on Console Log
8. Now you demand to run an coating to view the gimmick logs related to it
9. If you require to save the logs, Click on Save Full Log.

Conclusion

When an application on your gimmick crashes, it generates log of information designate us to the issue that was behind the clank. These gimmick logarithm help us to collect information about app-related issues and their diagnosis. Ultimately, these device logs play an important role in the testing of an application and control that everything is scarper smoothly.

Using App Live, you can use native device features to on a orbit of Android & amp; iOS device supported by BrowserStack. Using App Automate, you can on real mobile phones rather than the home testing grid. You canschedule a gratuitous runfor both the BrowserStack production before subscribing to a plan.

Related Guides