Reputation: 326
I have a situation: 1. Samsung 7 has a strange bug in my app. 2. This device is 10000 miles away from me.
What are the opportunities for debugging this device remotely.
When tester on the other side can do everything.
I tried adb tcpip <port>
but device ip can be only local(192.168.....
)
The rude way is to get Android Studio there and install team viewer on the phone. It's not working every time.
And when we have 1 hour intersection it's difficult to support.
Is there any other way?
Upvotes: 1
Views: 2180
Reputation: 686
You could try something like LogmeIn for Android - this way both devices will be in the same network.
Once done, just do usual adb connect ipadress
If t refuses to do so first, try enabling ADB over WiFi option
Upvotes: 0
Reputation: 14274
Developer Options
on the device. You should already know how to do that. Take Bug Report
and/or Bug Report Shortcut
settings. If you enabled Bug Report Shortcut
a Take Bug Report
option will appear when pressing/holding the power button.As for the APK you send to your user, make sure debugging is enabled, so you get all your log messages. If you obfuscate the APK, be sure you keep your mapping files handy.
Upvotes: 1
Reputation: 352
There are several options:
-Build APK and send it to the phone. Install and check/try again.
-Create Android Virtual Device identical to the model located remotely, install Samsung Android firmware.
There is no clear solution about debugging out of local network.
Upvotes: 0
Reputation: 76
If you have some idea of where the bug is happening, an option could be to set up something like http://www.acra.ch/ and send your tester a new apk.
This way when the bug is provoked, given you set up useful log events, you will receive information about the crash or bug. ACRA lets you include the LogCat as well, which is pretty useful.
Upvotes: 0