IssueTracker

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Please provide sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer: https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”.  Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the files to google drive and share the folder to android-bugreport@google.com, then share the link here.

Please find here the demonstration video: https://drive.google.com/open?id=15PEkr6H-LZehyGfNaq2iiLC317wpOSIJ
Bugreport: https://drive.google.com/open?id=1dwg-VMhIsLxTFnkCd4A-OLQPEaknj9ld

I am working on creating test account that you can use to reproduce the problem.

Thanks.

I created a test account that you can use. These are the steps.

1. Please install Mobile@Work from Google Play.
2. To register please launch it and tap on "Or register with server URL"
3. Enter eapp069.auto.mobileiron.com as server URL.
4. On next screen enter user name test and password Qwerty12
5. Go though provisioning, acquiring Device Admin, grant or deny location permission.
6. Certificate provisioning will start and you will see the issue.