SOTI Pulse Logo

Android+ "MobiControl has stopped working"

BR
Ben Ragland
Zebra (OVS) - Manhattan Associates

This was on a (multiple) Zebra WT6000 non-GMS running the latest of Lollipop/MX.

Right after enrollment into 14.1, my device would startup the MobiControl Agent app on the device and then the app would close, showing "MobiControl has stopped".

I've been getting this consistently on all of my WT6000s. Sometimes relaunching the Agent will work but I had one instance where the device showed the agent and the stage app still installed and I had to uninstall the agent and re-enroll the device using stage.

Anyone see this before?

Upgraded Agent is 13.5.0 Build 1327

Thanks,

Ben

mobicontrol android agent zebra has-stopped-working
Edited 7 years ago
Android
ANSWERS
MD
Matt Dermody Diamond Contributor
7 years ago

I experienced a similar thing this week on Zebra TC8000s running Lollipop with the same 13.5.0 build 1327 o a 14.1 (April 2nd) instance. From what I could tell it was only happening when I was connected to the devices via adb using scrcpy so I chalked it up as an anomaly. Are you sure that it's not just happening when plugged in via USB?

BR
Ben Ragland
7 years ago

This occurs with only an RS5000 tethered to the device right after enrollment.

MD
Matt Dermody Diamond Contributor
7 years ago

Running the latest Lifeguard update as well?

BR
Ben Ragland
7 years ago

Most definitely. I think there may be an issue with the agent. I also noticed that some package scripts are not processing the first go around until a force install and one of my 5 devices would not connect the agent to the server until a reboot of the device.

MD
Matt Dermody Diamond Contributor
7 years ago

Maybe confirm that the exact same agent version is actually installed at the Android package level?

TT
Tim Tassone
7 years ago

I am running into the exact same issue with the WT6000 running Lollipop with most recent Lifeguard update.  In this case we are running 14.1.6.1113.  Other devices (TC8000 and VC80) enroll without issue.  Did you ever find a resolution to this issue?

Similar Discussions