Forum Discussion
TanyaYatskovska
10 years agoSmartBear Alumni (Retired)
Hi Deepa,
Could you please collect some additional info on your device to help our R&D team better understand what is going on?
Perform the following on the device:
1. Run Command Prompt.
2. Navigate to the "<Android SDK>\Platform-tools\" folder. To do this, type:
cd <your_drive_letter>:\<path_to_the_Android SDK>\Platform-tools\
3. Execute the following command with Android Debugging Bridge:
adb shell logcat -c
4. Reproduce the problem.
5. Execute the following command with Android Debugging Bridge to generate the report:
adb shell logcat -d > dump.txt
The "dump.txt" file will be created on your machine where the "adb.exe" executable file is located.
Send the generated file to our TestComplete Support team with the description of the issue.
Thanks.
Could you please collect some additional info on your device to help our R&D team better understand what is going on?
Perform the following on the device:
1. Run Command Prompt.
2. Navigate to the "<Android SDK>\Platform-tools\" folder. To do this, type:
cd <your_drive_letter>:\<path_to_the_Android SDK>\Platform-tools\
3. Execute the following command with Android Debugging Bridge:
adb shell logcat -c
4. Reproduce the problem.
5. Execute the following command with Android Debugging Bridge to generate the report:
adb shell logcat -d > dump.txt
The "dump.txt" file will be created on your machine where the "adb.exe" executable file is located.
Send the generated file to our TestComplete Support team with the description of the issue.
Thanks.
Related Content
- 2 years agokrugerm