4

I have a really "simple" problem. I have an application that is internal to our company. The company uses the AirWatch browser to manager internal web apps, which is fine.

The problem is, I have no idea how to debug or see the Javascript execution in that browser. Is there a defined way to do this? I've spent some time trying to search, but we've come up with nothing.

JasonWilczak
  • 2,303
  • 2
  • 21
  • 37
  • did you ever manage to solve this? – SimonGates Jun 27 '16 at 13:50
  • Nope, as of right now, the only solution is the AirWatch team looking into it directly. We had to pull IIS logs and use Wireshark to verify requests from AirWatch to the MAG servers, but that is as much as we could get, no visibility into Javascript execution... – JasonWilczak Jun 28 '16 at 13:03
  • Yeah I gave up and had to resort to old school alert(variableName) style debugging.. Didn't help in the end as I had a problem with history.pushState and they have a very buggy implementation of it. – SimonGates Jun 28 '16 at 13:14
  • 1
    @SimonGates sorry to hear that, I think not having some developer debugging in place is a terrible implementation for something that is being touted as a secure enterprise standard option. Fortunately we are switching to use safari/chrome so this won't be an issue for us anymore. – JasonWilczak Jun 28 '16 at 17:26
  • Anyone since solved this, or has everyone just gone to another browser? – Dave Oct 10 '17 at 13:13
  • 1
    No solution. Our company switched to enabling other browsers (safari and chrome) to work through the network, so Airwatch is basically not used. Airwatch support stated they had no way to debug client issues... – JasonWilczak Oct 11 '17 at 20:20

1 Answers1

3

You can't debug AirWatch browser, only android and iOS apps using chrome and safari, when the device is connected via cable.

I usually implement a logging system that writes on a local log.txt file, and provide a button in settings to send the log file via mail.

Luca
  • 196
  • 9