Today we started seeing issues on the devices with Boxer installed. Appeared to impact 5.22.1 and 5.23 builds. Our SEG was running an older build of 2.0.9. Symptom was people would receive an alert that their device was not compliant with DeviceResponseStatus of 403 in the SEG logs which we dump to Splunk.
We updated our SEG to 2.16 and rebooted. Devices using the native client work fine without issue, but the 10 or so devices we have with Boxer installed stop being able to send/receive email. One odd thing we've noticed is that if we restart the SEG service Boxer clients will work for a few minutes and then start to timeout again.
These devices seems to show a message relating to "Device not compliant." We have attempted to disable the compliance policy but the issue persists.
Native clients are communicating without interruption. Only Boxer enabled (Android and iOS) are impacted. Some of the client combinations that are impacted:
| BoxerManagedAndroid | AirWatch Boxer (SM-G960U; Android 10) Version 5.23.0.1/2313 |
| BoxerManagedAndroid | AirWatch Boxer (SM-J700T; Android 7.1.1) Version 5.23.0.1/2313 |
| BoxerManagedAndroid | AirWatch Boxer (moto x4; Android 9) Version 5.23.0.1/2313 |
| BoxerManagediPhone | AirWatch Boxer (Apple iPhone; iOS 14.2) Version 5.23.0/6692 |
We have a ticket open but wondering if anyone else has seen this.
