Different ways of collecting Receiver logs from Android Device.

---

Instructions

There are two ways to collect logs from Android Devices using RfAndroid.
Mainly, we use the ‘Send Feedback > Request help from Support’ option that is available under ‘Receiver > Settings’ on the device.
 
Above option is not available in RfAndroid 3.9.1 and above.
Please find the screenshot below, left one is from RfAndroid 3.8.2 and right is from RfAndroid 3.9.2
 

 
“This is a known bug when connecting to stores which have Unified Experience enabled.”
 
Since, this is a known bug, ideally we are left with only one option to collect logs for troubleshooting and that’s using ADB (Android Debug Bridge)
Below article will give more information on ADB (Android Debug Bridge)
https://developer.android.com/studio/command-line/adb
 
We need to install it in Windows OS.
To use ADB with your Android device, you must enable USB debugging on your Android device. You’ll find this option under Developer Options on your device’s Settings screen.
 
Connect your Android Device with the Windows OS.
To test whether ADB is working properly, connect your Android device to your computer using a USB cable and run the following command: adb devices
You should see your device listed here.
 
Now, we need to create a receiverconfig.txt file on your Windows OS machine.
Add the line "LoggingLevel=verbose" in the file.
Save the file. (The file should be copied to /sdcard/ location of the Android device).
From the command prompt, type this command: "adb push receiverconfig.txt /sdcard/receiverconfig.txt" [This will push the file to logcat. Logcat is a third-party utility responsible for collecting logs at Android devices]
Restart the RfAndroid.
 
Now, you are ready to collect logs.
Reproduce your Android issue and run the following command.
Run adb logcat >”Name and location of the log file”
Ex- adb logcat >c:\temp\logcat.txt
This will use logcat to collect logs and save it as logcat.txt in the location c:\temp.
 
You can view this log using Notepad/Notepad++.

This software application is provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that: (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the software application be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the software application.

https://www.citrix.com/blogs/2015/06/02/mobility-experts-how-to-collect-android-device-logs-for-troubleshooting-xenmobile-issues/